I've run out of UARTs :(

[whoelseisbored (LiamHowe89)]

So I bought a Beitian Dual BN-220 GPS recently and had been excited to get it on my quad... until I realised that all 3 of my UARTs are in use
UART1 SmartAudio
UART3 SmartPort
UART6 SBUS

I'm tempted to bin off the SmartPort to free up that UART for my GPS. In terms of the telemetry to my Tx I only tend to find myself caring about RSSI... and that comes direct from my R-XSR anyway and not SmartPort. My battery levels are all setup in my OSD and obviously having my goggles on means I can't exactly use the telemetry on the Tx anyway.

The other option I've looked into (but it feels like a bad move) is to free up UART6 and use PPM from the R-XSR as my FC does have a PPM port. But as I understand (and please correct me if I'm wrong) this would decrease the number of available channels and also the signal would be analogue which would increase latency. I also have no idea how to go about doing this!

I guess the other option is to not use the GPS module... but that wouldn't be very fun! Haha.

Any thoughts at all? I'm aware that by getting rid of SmartPort would mean that my Tx wouldn't receive GPS data, so if my quad went down I'd have to check the DVR for coordinates etc.

[ched]

I think there is a FrSky fw that allows Fport so sbus and telemetry on a single wire! I guess Oscar would have a page on it. Hope that helps?

Oops corrected sport to Fport, stupid me.
While Fport is inverted there is a small solder pad for uninverted on r-xsr that can be used to connect Fport to a tx uart on an F4 no problem.

[badger1]

I was using firmware version 191128 for F.Port on my R-XSR & it worked fine on my F7 board, but F.Port is an inverted signal & I think you're on an F4 board.

you might do better to run SmartPort on softserial & map it to another pin - Oscar explains it better than me here:

https://oscarliang.com/betaflight-soft-serial/

[whoelseisbored (LiamHowe89)]

I think there is a FrSky fw that allows Fport so sbus and telemetry on a single wire! I guess Oscar would have a page on it. Hope that helps?

Oops corrected sport to Fport, stupid me.
While Fport is inverted there is a small solder pad for uninverted on r-xsr that can be used to connect Fport to a tx uart on an F4 no problem.

Well according to Oscar Fport is uninverted Link

I'm currently using that minuscule uninverted s.port pad... so does that mean that I can leave that one rigged up to TX3 and just disconnect SBUS from RX6 freeing up UART6 for GPS goodness?

I was using firmware version 191128 for F.Port on my R-XSR & it worked fine on my F7 board, but F.Port is an inverted signal & I think you're on an F4 board.

you might do better to run SmartPort on softserial & map it to another pin - Oscar explains it better than me here:

https://oscarliang.com/betaflight-soft-serial/

I actually flashed my R-XSR to FPORT_LBT_ACCST_191128 last night and now the bleedin thing wont bind. I'm wondering if my Jumper T16 might be set to FCC tbh. Guess I'll have to flash to FCC on the R-XSR and find out.

[badger1]

Well according to Oscar Fport is uninverted Link

where Oscar says "FPort is an uninverted protocol **", note the ** :

** Although the F.Port is a non-inverted protocol by design, currently the signal is still coming out of the SmartPort (S.Port) pin on the receiver, and the S.Port pin is normally inverted on Frsky receivers. This makes the F.Port signal inverted as well.

[badger1]

I'm currently using that minuscule uninverted s.port pad... so does that mean that I can leave that one rigged up to TX3 and just disconnect SBUS from RX6 freeing up UART6 for GPS goodness?

I think that if you have SmartPort working on TX3, then F.Port would work there too - once you load firmware that your Tx will bind to. 

it may need you to add:

"set serialrx_halfduplex = ON"

from CLI as F.Port is bi-directional - control Rx-->FC & Telmetry FC-->Rx - over a single wire.

but then yes, UART6 free for GPS fun.  :)

[whoelseisbored (LiamHowe89)]

I think that if you have SmartPort working on TX3, then F.Port would work there too - once you load firmware that your Tx will bind to. 

it may need you to add:

"set serialrx_halfduplex = ON"

from CLI as F.Port is bi-directional - control Rx-->FC & Telmetry FC-->Rx - over a single wire.

but then yes, UART6 free for GPS fun.  :)

Not quite sure how I missed the ** on the Oscar guide! Haha.

That's good to know! The other thing I'd thought about is that I've not disconnected the SBUS from UART6 yet and I'm getting a feeling that I've read somewhere that you can't bind until that's disconnected. So guess I need to get that done to try.

[atomiclama]

Just stick SmartAudio on a soft serial as it is only used when the VTX is changed and so won't load the FC too much, if you run Smart port on the Softserial you run the risk of loading up the FC and causing problems.

[badger1]

all you need is power to the Rx to bind - it doesn't care about SBUS/F.Port/whatever being connected.

[whoelseisbored (LiamHowe89)]

Ok so I've just flashed the FCC FPORT firmware to the R-XSR and now I can bind to it. Great... but now I can't FPORT itself working. So no receiver input. This is hurting my brain.

[badger1]

tried setting serial Rx to half-duplex?  see my post #5

[ched]

Ok so I've just flashed the FCC FPORT firmware to the R-XSR and now I can bind to it. Great... but now I can't FPORT itself working. So no receiver input. This is hurting my brain.

Don't forget you have to change BF to fPort on the config page!!!
Plus turn on Telemetry but you probably have that already?

[whoelseisbored (LiamHowe89)]

tried setting serial Rx to half-duplex?  see my post #5

Yep ran...
set serialrx_halfduplex = ON
set serialrx_inverted = OFF

My Jumper T16 is showing as bound and also telemetry is coming through. However the receiver tab in BetaFlight isn't showing any movement when the sticks are moved.

Don't forget you have to change BF to fPort on the config page!!!
Plus turn on Telemetry but you probably have that already?

In BF it's set to serial-based receiver and FrSky FPort in the config page.

Feel like I'm missing something really obvious 

[ched]

set serialrx_inverted = OFF

Try the opposite. Reason being that BF gets clever and tried to guess if it needs inversion by looking at settings and applies it automatically. So maybe try serialrx_inverted = ON.

[whoelseisbored (LiamHowe89)]

Try the opposite. Reason being that BF gets clever and tried to guess if it needs inversion by looking at settings and applies it automatically. So maybe try serialrx_inverted = ON.

Right, just done that and while it didn't break the telemetry it still hasn't made the receiver tab any better. Attached a screenshot below. The 'preview' model is spinning around like a nutter as well. Feels like the channels are mixed up maybe?

[ched]

Do you get any movement on the rx display on bf i.e. sticks, switches, pots etc?
Are you getting a correct Voltage in telemetry?

[whoelseisbored (LiamHowe89)]

Do you get any movement on the rx display on bf i.e. sticks, switches, pots etc?
Are you getting a correct Voltage in telemetry?

Nothing at all. None of the AETR or AUXs move whatsoever.
Voltage shows correct on my TX via telemetry.

[ched]

Have you only got the 0v,5v and Fport connected now? If so then if you are getting telemetry you must have it physically connected correctly, it must just be a software setting.
I guess double check config page that rx is set correctly and then just try all permutations of half duplex and inversion. Remember to power cycle quad after each change!!!!

[Bad Raven]

Well, the model on the Rx screen will be spinning as you have max negative Roll, Pitch and Yaw!

They should all be 1500.

Unlikely channels swapped as say TAER instead of AETR might do, as the three could not be full negative at the same time.

What does your Mixer screen look like in OpenTX on the Tx?

Consult Tx Monitor and check output of channels, should be Roll, Pitch and Yaw @ mid (1500) and Throttle at min (less than 1050). But does it?


Also in Betaflight CLI, what does the "Status" command show?

[whoelseisbored (LiamHowe89)]

Have you only got the 0v,5v and Fport connected now? If so then if you are getting telemetry you must have it physically connected correctly, it must just be a software setting.
I guess double check config page that rx is set correctly and then just try all permutations of half duplex and inversion. Remember to power cycle quad after each change!!!!

Yep got it wired as below...

Any idea what the (S) next to RX6 is? That's where SBUS was originally. Do you think it's worth trying FPort to TX6 instead maybe?



Yeh I'll go through all the different permutations as well.

Well, the model on the Rx screen will be spinning as you have max negative Roll, Pitch and Yaw!

They should all be 1500.

Unlikely channels swapped as say TAER instead of AETR might do, as the three could not be full negative at the same time.

What does your Mixer screen look like in OpenTX on the Tx?

Consult Tx Monitor and check output of channels, should be Roll, Pitch and Yaw @ mid (1500) and Throttle at min (less than 1050). But does it?


Also in Betaflight CLI, what does the "Status" command show?

Will check on this now :)

[whoelseisbored (LiamHowe89)]

Well, the model on the Rx screen will be spinning as you have max negative Roll, Pitch and Yaw!

They should all be 1500.

Unlikely channels swapped as say TAER instead of AETR might do, as the three could not be full negative at the same time.

What does your Mixer screen look like in OpenTX on the Tx?

Consult Tx Monitor and check output of channels, should be Roll, Pitch and Yaw @ mid (1500) and Throttle at min (less than 1050). But does it?


Also in Betaflight CLI, what does the "Status" command show?

I feel like I'm glad I put this in the newbie section I don't know if it's useful to know or not but when I connected to BF initially my TX was off and the preview on the receiver tab was normal looking. As soon as I turned on the TX it went mad again so I guess the connection itself is working. Haha.

My mixes screen is as below... (please excuse the angle)



When you say consult Tx Monitor... can you explain it as if I'm completely stupid?

The status command returns this...

Code Select Expand

# STATUS
MCU F40X Clock=168MHz (PLLP-HSE), Vref=3.27V, Core temp=45degC
Stack size: 2048, Stack address: 0x1000fff0
Config size: 3792, Max available config: 16384
GYRO=MPU6000, ACC=MPU6000
System Uptime: 580 seconds, Current Time: 2020-07-30T16:01:22.844+00:00
CPU:13%, cycle time: 127, GYRO rate: 7874, RX rate: 111, System rate: 9
Voltage: 1 * 0.01V (0S battery - NOT PRESENT)
I2C Errors: 0
SD card: Startup failed
Arming disable flags: CLI MSP
Thanks for your help on this guys! Going mad over here!

[Bad Raven]

The monitor is the screen most Tx have that shows each channel as a live bar graph, and as you move the sticks, the bars alter (hopefully!). It may or may not be actually looking like part of OpenTX, it might seem to be in the Tx firmware.  For example on the Taranis, and on the main screen as it powers up, you press "Page" once, don't know the sequence for your Tx, don't have one!

[whoelseisbored (LiamHowe89)]

Is it this? These are mine if so.



Quick update...
Updated to OpenTX 2.3.9 and setup the radio from scratch.
Reflashed the firmware again for R-XSR.
Tried all different permutations of serialrx_inverted and serialrx_halfduplex.

None of the above helped... AERT all stuck at 896... Feel like it's either the receiver that's gone batty or going to have to start from scratch on the FC.

[Bad Raven]

You have said AERT.  BUT.........Either TAER (based on stupid Spektrum which HAD to be different on near everything just to be awkward) or AETR (Futaba, FrSky, FlySky, etc) is normal and your Receiver screen is set to AETR.

BUT.......... you have a Mode 2 so Throttle left, Channel 3, which it is.

However, you have RH Stick left/right normally Roll or Aileron so Channel 1 as Channel 4!

Channel 4 is normally Rudder / Yaw.

Yous Status output in CLI was showing unable to arm due 1.............CLI (it would be, you are using it!!) and 2........... MSP.  MSP is the motor protocol and it is this which is stopping arming.

With regard  the receeiver actions, SOME FC need the battery connected as well as USB to show receiver screen correctly, some just need USB. Whatever, DO NOT WORK WITH PROPS ON!!!!!!!

[whoelseisbored (LiamHowe89)]

You have said AERT.  BUT.........Either TAER (based on stupid Spektrum which HAD to be different on near everything just to be awkward) or AETR (Futaba, FrSky, FlySky, etc) is normal and your Receiver screen is set to AETR.

BUT.......... you have a Mode 2 so Throttle left, Channel 3, which it is.

However, you have RH Stick left/right normally Roll or Aileron so Channel 1 as Channel 4!

Channel 4 is normally Rudder / Yaw.

Yous Status output in CLI was showing unable to arm due 1.............CLI (it would be, you are using it!!) and 2........... MSP.  MSP is the motor protocol and it is this which is stopping arming.

With regard  the receeiver actions, SOME FC need the battery connected as well as USB to show receiver screen correctly, some just need USB. Whatever, DO NOT WORK WITH PROPS ON!!!!!!!

I only said AERT because I was reading down the channels on the left (shown below)...


Map is set to AETR1234 as is TX.

Props are always off

[ched]

Just a quick check, what lights are on the rx? I think in Fport you just get the green to flash when it's receiving from tx.
Also double double check you flashed the correct FW as FrSky are hiding the older protocols but if it's bound I think you are OK but check anyway.

[whoelseisbored (LiamHowe89)]

Just a quick check, what lights are on the rx? I think in Fport you just get the green to flash when it's receiving from tx.
Also double double check you flashed the correct FW as FrSky are hiding the older protocols but if it's bound I think you are OK but check anyway.

So when it's bound it sits with a solid green light.
Yeh checked because I nearly went with v2 but apparently that stops the T16 from binding as a 3rd party (although I'm hearing people have sorted that now).

It's so frustrating, pretty sure it's cuz this FC is rubbish tbh. Think I may end up flashing it and starting again to see if that sorts it. Might try another UART first though.

[whoelseisbored (LiamHowe89)]

Just found this on Banggood Q&A for the FC...

Q: "Has somebody managed to get FPORT (FrSky Protocol) working? I don't get it and need help"

A: "Yes. Use uninverted signal on TX1 with serialrx_halfduplex = ON and serialrx_inverted = OFF. TX6 did not work."

https://www.banggood.com/qa-answer-399319-1.html

Think it's got to be worth a shot.

[Bad Raven]

SO, from that last post just realised which FC we are actually dealing with, and bad news, I have one that proved total carp (though I did get it working as far as my FrSky Rx would work it and control it.......... badly!!)

Frankly I think you may well be on a hiding to nothing fighting it any further, I have put many hours effort into mine, all wasted!

I like the Matek F405 Std budget unit, esp with its ribbon cable connection to the Matek Hub, I have quite a few in use. They have all been easy to set up and stable once set. There are F7 versions and there is an AIO version of thre F4, too.

UK Supply:-   https://www.hobbyrc.co.uk/matek-f405-std-flight-controller