TBS source one v2

[badger1]

I agree with what Ched said (mostly).  you only +5V & GND to bind the Rx.  are the lights on the Rx indicating it's bound?  I'm not terribly familiar with the r9mm, but if it does telemetry, are you getting Rx supply voltage & RSSI back from it?

If it's rx signals to the FC then I thought, with right fw, it had non inverted sPort which just requires a tx uart?

Rx FW doesn't flip the inversion on SBUS/SmartPort/FPort (if that's what you meant Ched), but the F7 FC can do it in hardware, you might just need to toggle on the console/CLI it if it doesn't detect it - see my post #56.

[ched]

Rx FW doesn't flip the inversion on SBUS/SmartPort/FPort (if that's what you meant Ched), but the F7 FC can do it in hardware, you might just need to toggle on the console/CLI it if it doesn't detect it - see my post #56.

Sorry I wasn't clear, the r9mm rx has a dedicated inverted sPort pad. So you don't need to worry if fc can un-invert or toggle in cli, just use the 'inverted sPort' pad.

As for FW, I think getting a matching FW on module and r9mm is critical.

[trebor]

It must be something like that, the Rx lights look as though they bind but get no movement on the controls in Inav. When I disconnect the battery and re connect then Rx green light has gone.
Trouble is on the Frsky site downloads for my module is listed as discontinued, when I last looked there was at least 6 different downloads but the one I wanted had the Flex firmware. I just had another look and all there is now for my module is 1 to choose from and its listed as a fix so they have changed it again My module came free with the Tx so its not the latest 2019 edition that runs Access firmware.

[ched]

. I just had another look and all there is now for my module is 1 to choose from and its listed as a fix so they have changed it again My module came free with the Tx so its not the latest 2019 edition that runs Access firmware.

I think if you download it the single zip has 3 different versions. FCC, EU and Flex!

[trebor]

Update, I re-installed the Flexfirmware on the r9m module and r9mini rx and the Tx binds and holds  but still no controls on my sliders in Inav receiver yet  WTF this quad will fly even if I sling it over the fence.

[ched]

OK so binding is now good, well done.
Fist off which output from r9mm are you using? Which pad on FC is it connected to?
From there we should be able to narrow down the issue.

[trebor]

Well I have the rx wired with 3 wires, the smartport / f port wire goes onto flight controller Tx3

Ps, I did find a bit more info here link

[ched]

I assume you are not using the sbus out on the r9mm? Only reason I ask is early on using frsky I couldn't get an r-xsr working until I realised the pin to flash fw is sport and sbus pin is signal output!!! Took me a while to work that one out   

So you are using an inverted pad. I think you need to ucs the cli commands:
set serialrx_inverted = ON
set serialrx_halfduplex = ON
BUT I don't know the equivalent for iNav. You might need to play with the
set serialrx_inverted = ON and = OFF as depending on BF version ( I know you are using iNav) some auto invert when you select uart and sPort some don't so it might be similar on iNav.
Have a look at https://oscarliang.com/setup-frsky-fport/
This is about iNav an an F4 back in 2018/19 but it may give you some clues: https://github.com/iNavFlight/inav/issues/3743

Is it worth flashing sbus version on r9mm and wiring that to the sbus pad just to check rx is working?

[ched]

Just found this http://www.mateksys.com/?p=4488 I seem to mention r9mm inav and f7 etc?

[badger1]

you obviously need to have the FPort firmware on the Rx, & the Rx serial protocol set to FPort in iNav, then toggle:

set serialrx_inverted = ON/OFF
set serialrx_halfduplex = ON/OFF

there are four combinations to try & one of them should work.  under BF my R-XSR needed both set to "ON".

[trebor]

This is all too confusing    My R9mm Rx has pin 1 sbus out, pin 2 s.port/fport, pin 3 gnd, pin 4 v_in, pin 5 inverted s.port.
I put my signal wire on s.port/ f.port connection.
How do I know if my FC needs inverted or not as I cannot find anything written down. I have Flexfirmware on the module and Rx now but it might be the weekend I get the chance for another look at it now 

[badger1]

This is all too confusing   

it's really not

My R9mm Rx has pin 1 sbus out, pin 2 s.port/fport, pin 3 gnd, pin 4 v_in, pin 5 inverted s.port.
I put my signal wire on s.port/ f.port connection.

that sounds fine

How do I know if my FC needs inverted or not as I cannot find anything written down. I have Flexfirmware on the module and Rx now but it might be the weekend I get the chance for another look at it now 

I'm assuming iNav is pretty close to BetaFlight here

1. Ports page:

you said you have the SPort/FPort connection wired to Tx3, so select "Serial Rx" for UART3 & reboot

2. Configuration page:

select FPort for the Receiver protocol & reboot

3. check in the Receiver page to see if you're getting Tx inputs

4. if not, go to the CLI page & type:

set serialrx_inverted = ON
set serialrx_halfduplex = ON

& reboot.  go back to Rx page & check.

if its still not working, try each of these combinations in turn:

set serialrx_inverted = ON
set serialrx_halfduplex = OFF

set serialrx_inverted = OFF
set serialrx_halfduplex = ON

set serialrx_inverted = OFF
set serialrx_halfduplex = OFF

if it's still not working, send it to me & I'll get it working.  I won't send it back, but I'll get it working 

[ched]

This is all too confusing    My R9mm Rx has pin 1 sbus out, pin 2 s.port/fport, pin 3 gnd, pin 4 v_in, pin 5 inverted s.port.
I put my signal wire on s.port/ f.port connection.
How do I know if my FC needs inverted or not as I cannot find anything written down. I have Flexfirmware on the module and Rx now but it might be the weekend I get the chance for another look at it now 

It is confusing. This is my belief: FrSky's sBus/fPort is an inverted digital protocol it originally came from Futaba (same as the frsky x9d form factor  ). I believe that the rx output basically sits at 3.3 or 5v (I don't know which) and the output goes low to indicate a signal from tx.
iBus is from FlySky and is sort of inverted sBus. So the signal sits at 0v and then goes high when receiving a signal from tx.

To add further to the complication BetaFlight, at some version, I don't know which one, automatically un-invert a sBus signal on f3 and f7 boards when you say you are using sbus. I guess iNav does the same?

So if you are using the sPort/Fport output from the r9mm it should be connected to a tx uart Not a softserial uart!. Set the rx uart to serial and the config to serial and fport. Then you have to try the 4 variations in the cli ( yes and no in all combinations of both commands) to see which one works.

It's stupidly way over complex but is just playing with the cli settings, remembering to power cycle each time.

Hope that the above makes some sort of sense? As I said the above is my interpretation and may not be 100% correct 

[badger1]

To add further to the complication BetaFlight, at some version, I don't know which one, automatically un-invert a sBus signal on f3 and f7 boards when you say you are using sbus. I guess iNav does the same?

no, it's a hardware thing.  you can still flip a signal in software, but that's softserial, which isn't what we want (especially on an F3 board!).

for whatever reason, F3 & F7 chips have built-in hardware inverters (or rather, for inverted signals, de-inverters) on all UARTs while F4 boards don't.  F4 FCs that accept a native (ie inverted) SBUS signal have an inverter built onto the FC board between the pad & the chip to flip the signal.

your F7 FC definitely *will* handle a native (ie inverted) SBUS/FPort/SPort signal, it's just that you might have to toggle the two settings I referenced depending on whether the inversion is detected and/or how BF/iNav has told the chip to expect the signal.

[ched]

To add further to the complication BetaFlight, at some version, I don't know which one, automatically un-invert a sBus signal on f3 and f7 boards when you say you are using sbus. I guess iNav does the same?

no, it's a hardware thing.  you can still flip a signal in software, but that's softserial, which isn't what we want (especially on an F3 board!).

Yes the f3 and  f7 chips have hardware inverters built controlled by BF software. Depending on the version of BF you are using, when you select frsky and sbus or fport BF can automatically activate the in built inverters. Older versions of BF did not do this, so you had to set it manually in cli!!! Newer versions of BF activate the inverters according to your selections of frsky and sbus or fport.

As for softserial the reason for mentioning it was that some people don't realise that it's not suitable for control signals and try and use a softserial for connecting the rx. It can be used for Smart Port and can have software (BF) inversion applied if necessary.

So playing with the 4 options in the cli is the way to go.