Omnibus F4 Pro V3 Pinout. AGND AGNO RAM RAM WUT VIN O SBUS 5V GND 0 000000 UI 000000 GNDO Oswc Omn ibusF4- 5V GND 0 PWN4 5V GND. FC: Omnibus F4 Pro AIO, this is the v2 / pro version, with the blackbox SD card reader onboard, built-in current senor and OSD. Since this is a new build, so I decided to go to F4 (I was using Naze32 F1) for longer future proof, and I like the idea of built-in OSD supported by betaflight and current sensor.
Zeta FX-79 Buffalo Build - Port planning, Smartport and RSSI
Serial Port Planning
The Omnibus F4 Pro V2 offers 3 UARTs.- UART1 - Used for SBUS
- UART6 - Available
- UART3 / I2C - Available if I2C is not needed
My Ublox Neo-M8N GPS with Compass module will need UART6 for the GPS, and the I2C pins for the Compass functionality. Unfortunately, I want to do Smartport as well, but don't have a UART. So, instead, I'll use softserial for the Smartport connection.
Omnibus F4 Pro Softserial Telemetry
My configuration will be as follows:
- UART1 - Used for SBUS
- UART6 - GPS
- UART3 / I2C - Compass
- Softserial - Smartport
Smartport
Omnibus F4 Pro Diagram
The Softserial ports are available on the Omnibus F4 Pro V2 via two pads on the front of the board. I followed the FrSky SmartPort using SoftwareSerial procedure at the bottom of the Omnibus F4 page. They call for a 1k ohm resistor between the RX and TX pins. I had one in 0603 in my parts bin, so I put it between the pads, and then attached a small wire-wrap wire to the RX pin. It ended up working fine.
There's the resistor, temporarily sitting on top of the processor. I circled the two pads it's going to be crossing below.
Here's the resistor installed, with a bit of Wire Wrap wire connecting to the RX pin.
After confirming that all worked well, I went ahead and secured this wire with a dab of glue to the top of the processor chip, for strain relief.
In order to use the Softserial port, it needs to be enabled in the iNav Configurator.I enabled Softserial, and while I was at it, also enabled telemetry.
After a reboot, I went into the ports page, found the Softserial port, and configured it for Smartport at 57,600 bps, as suggested.
The final step was to go into the CLI and apply two settings:
set smartport_uart_unidir=OFFHaving done that, I was able to go onto my transmitter, do a 'discover', and telemetry values populated from the flight controller.
set telemetry_inversion=on
One additional note. The GPS telemetry does not appear for a 'discover' on the radio until you have a GPS lock. This caused me quite a bit of frustration. Once the telemetry is discovered, it will be on the list on the radio, thereafter. You do not have to rediscover it after it is in the list.
RSSI
The Omnibus F4 V2 uses a tiny little pad in the middle of the board to receive RSSI data from the receiver. Many people are soldering a small wire to the pad, and just hanging it off the Flight Controller, with a bunch of glue and hope holding it in place. I didn't really like that solution. Instead, I opted to hijack the RAM pins to make the RSSI externally available.
Omnibus F4 Pro Soft Serial Case
The RAM pins on the Omnibus F4 pro V2 are wired together, but otherwise isolated, if you do not solder a jumper elsewhere on the board, linking them either to VCC or the 5v rail. Since I left the jumper undone, the RAM pins are just tied to each other. Since I'm powering my Camera and VTX via an external wiring harness, the RAM pins are unused.
I soldered a small jumper from the RSSI pad to one of the RAM pins. I will then solder a heavier gauge wire into the other RAM pin hole, and connect that to the wiring harness going off to the receiver. This should provide greater strain relieve for the RSSI jumper. I think this is a much more resilient solution. Here's the jumper wire going to one of the RAM pins. This picture does not illustrate the wire harness leading off the board.