Omnibus F4 Nano v6.1 pinout

Hardware Other Hardware
98

i see you‘re using copter stable 4.04. as for now, you‘ll find that alt config option in latest (master) firmware only.

99

Okay, I see. I thought that your changes is included in the most recent (4.0.4) stable version since your PR is merged before the new version is announced but I was wrong. Next time I will check it on git directly. Thank you for your help.

100

Hi all, I have a R1 + plus jumper and I would like to use yaapu script with FC omnibus F4 nano V6.0. I need the S.port and therefore with F4 a non-inverting pad on the rx. I connected the SERIALI 1 of the FC but I cannot read the telemetry on S.port. On the RX I have not updated the FW.

The question is:

on nano V6.0 is it correct to connect S.port to SERIAL 1 pad TX1 on nano v6.0?

Thanks

101

First post here.
MP 1.3.74 with ArduPlane v4.0.7 on Omnibus F4 nano v6.2
BRD_ALT_CONFIG = 1, but no SERIAL4 ??

What I am missing?

br

102

You are missing a Matek H743-Mini.
Just kidding (kind of)

Did you read the notes here?
https://ardupilot.org/copter/docs/common-omnibusnanov6.html

103

I did.

… and there and in this thread here SERIAL4 shows up. Might be too dumb to see SERIAL4.

Broodie, who had the same question, seems to have given up.

104

Maybe get some clues from the HWDEF file:
*use RX3 / TX3 pins as USART3 = SERIAL4 in BRD_ALT_CONFIG = 1

I think the problem is there are several .x versions of this board. Try 4.1-dev firmware.

1 Like
105

@nostromo123 what @dkemxr said. V6.X support only in master as for now, including alt configs for SERIAL4

106

First of all, thanx. That was fast.

Have to say, I am new to arduplane. 1st was a CC3D mini … no problem. 2nd a Matek F405STD … no problem.

But I needed another small FC and the CC3Ds are not available any more. Someone recommended the F4 nano, but what a c**p.

Got it now, but I used QGC.

Onboard parameters for Vehicle 1

Stack: ArduPilot
Vehicle: Fixed Wing
Version: 4.1.0 dev
Git Revision: 87564f14

Vehicle-Id Component-Id Name Value Type
.
.
1 1 SERIAL0_BAUD 115 6
1 1 SERIAL0_PROTOCOL 2 2
1 1 SERIAL1_BAUD 57 6
1 1 SERIAL1_OPTIONS 0 4
1 1 SERIAL1_PROTOCOL 2 2
1 1 SERIAL2_BAUD 57 6
1 1 SERIAL2_OPTIONS 0 4
1 1 SERIAL2_PROTOCOL 2 2
1 1 SERIAL3_BAUD 38 6
1 1 SERIAL3_OPTIONS 0 4
1 1 SERIAL3_PROTOCOL 5 2
1 1 SERIAL4_BAUD 38 6
1 1 SERIAL4_OPTIONS 0 4
1 1 SERIAL4_PROTOCOL 5 2

Any recommendation for a small FC to replace that omnibus thing, at the moment I am not happy with it.

br

107

see https://ardupilot.org/copter/docs/common-autopilots.html for reference. actually not too many nano size options out there currently. matek has some small footprint H7 controllers coming up, not widely available yet afaik.

what is it you don‘t like about the omnibus?

108

As I suggested, Matek H743-Mini. What doesn’t it have is the question.

109

Maybe I am just missing the Revo mini …

But besides, would be nice to have a note on that page
https://ardupilot.org/plane/docs/common-omnibusnanov6.html
about SERIAL4 being only available in latest firmware.

Have to admit, I was nearly giving up with SERIAL4. Then I found this thread here. Reading the posts, my frustration on that omnibus only increased.

But thank you here for giving a hand. br

110

Just a note that might help a few folks. I set up my Airbot F4nanoV6.1 first on cleanflight with my GPS/compass combo.
In cleanflight, I2C is on the PPM and PB9 pads on one side of the board. The GPS is connected to TX6/RX6 also on pads right next to the I2C pads.
In Ardupilot, the same card, same GPS, the GPS connects to the same TX6/RX6 pads, but the I2C moves to the RX3/TX3 PINS in the triple row of through-holes.

This worked for me and might help you, there are probably other setups but I wasted a few days trying to figure out why I had compass in cleanflight but not when the same hardware was flashed with ardupilot.

I also ended up using the WS2812 (LED) pin as PPM in.

Also thanks to all the folks who commented in this thread, it was very helpful to me.

111

Hi everybody;

Recently I purchased an “Omnibus F4 nano v6” (Ya, the Airbot sent me a V6.2), a “Flysky FS-i6X Transmitter with iA10B 10CH Receiver - it’s a two-way radio transceiver” and a “BN-880 GPS+Compass Module” to upgrade my old Cheerson CX-20 Quad (I wanna keep Motors and ESCs only), but I’m confused how to do the wiring.

Is it possible to have all options at the same time (GPS, Compass, and Telemetry) on this FC?

Any wiring diagram suggestions?

112

If you do a Google search for “arducopter omnibuss f4 nano” the top link that’s returned is the Wiki entry.

113

If you mean this: https://ardupilot.org/copter/_images/nanov6.jpg, this is for V6, not V6.x

114

That link is for:

Omnibus F4 Nano V6 and V6.x

Omni F4 nano

115

Is anyone using the SmartAudio or CameraCOntrol pads for anything? AFAICT they are not in the .hwdef. I want to use them as additional PWM outputs.

116

I’m new to mission planner and ardupilot so bought an Omnibus F4 nano v6.2 as its cheap to experiment with.

I have a DSM2 spektrum RC remote receiver from a AR6200 unit which I have connect to GND, 3.3v and WS2812 (Black, Orange, Grey).

I have set on SERIAL1,2,4 :
Baud to 115
Protocol to 23
Options to 0

I am not getting any joy in making the Spektrum receiver do anything. It momentarily blinks its orange light on powering up the omnibus but I cant get the bind DSM2 to work in Radio Calibration.

Serial 3 is connected to Ardusimple F9P using pads TX6 & RX6 - this is working fine and I’m getting GPS.

I’m using Rover 4.1.0 OFFICIAL and Mission Planner 1.3.75

Are there any other config options I should be looking at?

117

Turns out the transmitter I was using was DSMX and the EU in all there wisdom decided to make it illegal for DSM2 to work with DSMX. The rest of the world is fine.

I got the receiver paired with a DSM2 radio then moved the remote receiver to the Omnibus and connected it to WS2812 and I can read inputs from the radio.