Ok....

The facts......Betaflight F3 running betaflight 3.1.7;  Taranis TX; XSR RX; SBUS hooked to UART 2;  Softserial on UART 1;  UART 3 unused.  Everything is set up correctly in the ports and configuration tabs.  I would post screenshots of that, but I am currently headed out of  town and do not have the quad with me.  All ESC's are operational and wired correctly.  Channel mapping IS correct.

Issue......The RX is  bound to the  TX, but when everything is on, the the sliders for channels 1-4 (AETR1234) appear to be totally ignored.  I have switches set up on AUX channels 5 - 7 and they appear to work perfectly.  I am arming with a switch and according to the modes tab, it is working  correctly, but the board will not arm.  However, it DOES beep when I switch it  into Angle or Airmode.  I am thinking about switching SBUS to UART 3 to see what happens?  I would think all the channels would  work or none would work??

I'm befuddled (stop laughing Scotty).  Any and all help would be appreciated.  Thanks folks.

If i remember correctly i read about this problem being solved by flashing to an older version, then flashing 3.1.7 again...

By older i mean 3.0 or earlier which should ensure that everything gets erased.

In order to not set up everything manually again, you can put "diff" in CLI, copy that, and paste it back in when you flashed back to 3.1.7.

PS: Also check that your configurator did not auto-update to 3.1.2 (seems it was put on chrome store by mistake). Configurator 3.1.1 should be fine.

Not laughing (why would I laugh?)

I've got one of these boards, but I use Spektrum so probably not much help (I also haven't wired mine up yet). Curious about your softserial though. Are you not using the dedicated softserial on row two? And are you using the dedicated SBUS port on the last row? (which is what I have to use with Spektrum). If so, you did bridge the 5V jumper, correct? Sorry for just questions and no solution...guess I'm befuddled too.

(29-Jul-2017, 05:55 PM)fftunes Wrote: If i remember correctly i read about this problem being solved by flashing to an older version, then flashing 3.1.7 again...

By older i mean 3.0 or earlier which should ensure that everything gets erased.

In order to not set up everything manually again, you can put "diff" in CLI, copy that, and paste it back in when you flashed back to 3.1.7.

PS: Also check that your configurator did not auto-update to 3.1.2 (seems it was put on chrome store by mistake). Configurator 3.1.1 should be fine.

Hey fftunes...thanks for the response.  I had not read that and I've been doing a bit of research on it.  The board came with 3.0.1 on it and I brought it up to 3.1.7.  So are we saying that I should "reflash" back to 3.x.x and then bring it up to 3.1.7 again?  Interesting note.....I have a machine with an X-racer board that is running betaflight 3.1 and under the receivers tab NONE of the siders are active, but the thing flies perfectly.....go figure.

Anyway thanks for the response, when I get back home on Tuesday I'll give it a shot and I am familiar with the Diff" command.  Thanks a bunch!

(29-Jul-2017, 06:53 PM)sloscotty Wrote: Not laughing (why would I laugh?)

I've got one of these boards, but I use Spektrum so probably not much help (I also haven't wired mine up yet).  Curious about your softserial though.  Are you not using the dedicated softserial on row two?  And are you using the dedicated SBUS port on the last row? (which is what I have to use with Spektrum).  If so, you did bridge the 5V jumper, correct?  Sorry for just questions and no solution...guess I'm befuddled too.

"Not laughing (why would I laugh?)"......perhaps you'll remember the ESC wiring fiasco I had on the F2F frame?    It was said in humor my friend.  No, I am not using the dedicated softerial on row two and to tell you the truth, I am not sure why I'm not.  I knew it was there.  The soldering was a little easier to get to on UART  1, but perhaps I should rethink that.  I did use the dedicated SBUS row to hook into.  I think it and UART 2 (3 rows up from the SBUS row)are the same thing.  I did bridge to 5V for the XSR and Ive got I bridged to VBAT for the VTX and I am powering the camera from that.  Sometimes asking someone a question is the best way to get them thinking about alternatives and I always enjoy hearing your perspective Scotty, Thank you!!

(29-Jul-2017, 07:45 PM)sirdude Wrote: (...) The board came with 3.0.1 on it and I brought it up to 3.1.7.  So are we saying that I should "reflash" back to 3.x.x and then bring it up to 3.1.7 again?

I only remember one guy on rcgroups that reported the exact same symptoms, and for all i remember that's what he did to fix it... not that i could explain why it could help lol.

Did you have "full chip erase" enabled for flashing? Afaik should work on f3 boards... plus, i think there's also other ways to restore defaults, but not sure if in GUI or CLI, maybe that could help too.

(30-Jul-2017, 01:21 AM)fftunes Wrote: I only remember one guy on rcgroups that reported the exact same symptoms, and for all i remember that's what he did to fix it... not that i could explain why it could help lol.

Did you have "full chip erase" enabled for flashing? Afaik should work on f3 boards... plus, i think there's also other ways to restore defaults, but not sure if in GUI or CLI, maybe that could help too.

Understood.  I did have "full chip erase" enabled.  I'll try reflashing it when I get back home and will let you know what happens. Thanks again! 

UPDATE: @fftunes, you were correct. I took the board back to 3.0.1 (which is what it was shipped with and then flashed back up to 3.1.7. Everything is now working as it should. Thanks for the tip!

Glad it worked it's somehow weird especially since your board came with 3.0.1 to begin with, but then again, maybe it has something to do with the configurators as well...