I don’t think this matters. Perhaps Basti @vierfuffzig can help, he did the config work on the Omni Nano. My remaining Nano has BF flashed currently or I would test this.
@Alberto_Ds @dkemxr sorry i can’t really help with the actual port settings as don’t have any fport compatible hardware to test with.
other than that i can confirm that the originial OmnibusF4NanoV6’s SERIAL1 = USART1 is a plain full uart that requires no individual settings beyond what is usually required to use FPort on any plain F4 board’s serial port.
alberto, just to make sure, when you say “OmnibusNanoV6.0” are you referring to the original V6 board version with the micro-usb connector, NOT the newer one with USB type C socket?
This just occurred to me. Which firmware Rev ae you using? 4.1-dev hopefully?
Hi all,
I am using old 6.0 with micro usb port (no new 6.1 or 6.2) and fw stable 4.0.5. I am using the FC TX1 pad connected to the TX pad on external inverter. I also tried the FC TX1 pad connected to the RX pad on an external inverter.
@dkemxr
Can it make a difference using fw 4.1? I am using 4.0.5 with a patch to receive sat galileo as well.
Yes, I think it can. From the top of the Wiki page:
FPort Receivers
Support for FPort/FPort2 will be in firmware revs 4.1 and later.
Thanks Dave, then I try the 4.1 dev! But the correct physical connection with external inverter which would it be? TX or RX pad?
I tried with dev 4.1 but besides having strange errors (ie prearm bad logging), I also remember trying the same RX jumper R1 on FC Kakute F4 FW copter stable 4.0.5, without external inverter, and it worked. The radiomaster showed all the telemetry parameters correctly and not the usual 3/4 that I see with the FC Omnibus nano. So also in the 4.0.5 version there is S.port support
Sure there is but you are talking about Fport right?
S.port … This is my RX:
[14,23€ 40% OFF]Jumper R1+ RC Mini Receiver 16CH Sbus RX Compatible Frsky D16 Transmitter Radio Remote Control for RC Drone FPV Racing Multi Rotor RC Parts from Toys Hobbies and Robot on banggood
Well, this is the Fport thread so ignore everything I said 
ok but fport is not the same as sport with the added possibility of giving “commands”?
Fport is RC and telemetry combined in one protocol requiring only one port. If you had the Jumper R1F then you would be in the right thread.
Ok, I try to open new post in this thread 
I like that inverter, I dont see any charge pump caps, so its not a rs232, and more specifically, not subjecting a stressing +6V the S.Port / F.Port pins on my receivers. Can you see what is marked on the top of the chip (or picture) and post back what you find? tia
This is my inverter. green tx to tx1 FC , grey rx not connect, red Vcc to FC. violet GND to FC, yellow to S.port RX, black to gnd RX
Hi, I do not know, if I am right in this thread: I tried to get F.Port working using a H743 wing and XSR.
I connected the s.port pin of the xsr to RX6, set BRD_ALT_CONFIG to 1, RC options to 8, Serial protocol to 23, options to 15 and left baudrate at 57. The rc control data gets through (stickv alues are displayd correctly on gcs) but yapu does not get any telemetry (rssi and rxbat work, so I get telemetry from the RX). Any ideas?
Hello ,
I have exactly the same problem like you Simon, I already check different settings but impossible to recive th telemetry to my radio with H743-wing
I already check with this autopilot the Spoprt cofig with inverter ( only for telemetry /withouth pwm) and the problem is the same : impossible to recive th telemetry to my radio
Configuration
- H743-wing or F765-wing
- R9 Slim+ ota ( flashed with F.port version firmware or Sport version + inverter ony for trmemetry)
- Ardupilot V4.1.0dev (7a82898e)
Precision : the same Sport receiver (with the inverter) work good with another autopilot (Cuav5 nano with another version of ardupilot)
Any ideas?
Thanks
There seems to be a discrepancy between 2 sources of info for the F765-Wing.
In the board description it says:
It supports all RC protocols, however for FPort the receiver should be connected to T6 and SERIAL7 configured as described in FPort section.
The Fport section says:
UART6 RX can now be tied to receiver FPort. This board requires a unique configuration:
But I think the defining source is the Hwdef file:
as an alternative config setup the RX6 pin as a uart. This allows
- for bi-directional UART based receiver protocols such as FPort*
- without any extra hardware*
PC7 USART6_RX USART6 NODMA ALT(1)
I have also tried with serial options 7 and on tx pin, does not work either.
I just realized, that I had another UART set to S.Port Passthrough at the same time (although no S.Port reciver was connected). Could this be an issue (like it is impossible for two seperate uarts both to be F/S.Port Telemtry)? I can not test this currently as the FC is in use
Yes, this is an issue