Airbot Asgard v2 / Omnibus F4 AIO v2 (24amp 4-in-1 ESC with Dshot + Flight Controller)
The Airbot Asgard v2 / Omnibus F4 AIO v2 is attempting to take the Omnibus’ already sterling reputation for innovation, performance and stability to the next level! What you see before you is the latest iteration and stab at combining a 4-in-1 ESC and FC in the Airbot Asgard / Omnibus F4 AIO. The Asgard v2 / OMNIBUS F4 AIO v2 boasts a 24amp 4-in-1 dshot compatible ESC built-in, BetaFlight OSD, STM32F405 MCU, Current Sensor, MPU6000, 5v 3a BEC and a MicroSD card black box at a weight of just 14.1g. This is going to be like any other Omnibus F4 flight controller, in that you’ll be able to tune your PID’s using your transmitter, and use the drag and drop OSD setup in the OSD tab of the BetaFlight Configurator, but with the added bonus of SERIOUSLY cutting down the amount of space needed for your stack. Slapping on the Asgard v2 / Omnibus F4 AIO v2 means a potential for 5-10mm stack heights and with the direction everything’s gone, this appears to be the direction everyone wants to go. The Asgard v2 / Omnibus F4 AIO v2 may be the first legit 20+amp AIO flight controller to adequately serve as a PDB, ESC and Flight controller in one without frying the flight controller when treed with beacon’s going off.
Airbot has stated they will offer cheap repair/replacement service of this board/ESC’s in the event of the unthinkable. That being said, we recommend you verify ESC settings and configure appropriately for the motor protocol you’ll be using.
For discussion and information on the Airbot Asgard v2 / Omnibus F4 AIO v2, check out the thread HERE
As if you needed more incentive, we are offering $45 no questions asked replacements for our customers. This covers electrical damage and fried esc’s if that should ever occur. It’s super simple, you just contact us, we send you a link to the replacement board, you pay for a replacement and a couple days later you’ve got a brand new Asgard!!!
- STM32F405 MCU
- 24A Dshot 4-in-1 ESC
- Drag and drop OSD configured via BetaFlight Configurator
- SBUS/PPM + DSMX Ports
- 5v1.5a Clean Sbec /w On-Board Video Filter
- Built-in Current Sensor
- Built-in PBD
- 2-4s LiPo compatible
- 30x30mm w/ M3 holes
- Weighs just 14.1g!!!
Dshot Highlights and advantages over other protocols include:
(if you want seriously in-depth, go HERE)
- no signal jitter.. if the FC sends 1375 the ESC will receive 1375
- high resolution (2048steps)
- no oscillator drift (no more calibrating ESC’s)
- more robust against spikes
- safer as every singnal has a CRC (cyclic redundancy check)
- maybe later some goodies like having the ESC’s beep with the buzzer signal or things like that
If you’re looking for more info on Blheli_S, click HERE. The highlights of the Blheli_S protocol are as follows:
- BLHeli_S is an improved version of the base BLHeli code.
- BLHeli_S delivers a throttle response that is Smooth as Silk, and the main factor contributing to this, is that it uses hardware to generate motor PWM. Two MCUs support this for BLHeli_S, namely the BusyBee1 at 24MHz (EFM8BB10F8) and the BusyBee2 at 48MHz (EFM8BB21F16).
- BLHeli_S will have the same good Sync holding properties as base BLHeli. Maybe even better.
- BLHeli_S generally does Startup better than base BLHeli.
- BLHeli_S does damped light. Only.
- BLHeli_S has motor PWM that is Synchronous to the MCU master clock, as it is generated by hardware. This makes the motor Silent.
- BLHeli_S has very Small throttle Steps. The resolution varies between hardware configurations (MCU clock speed and driver type), and is between a nominal 512 steps and 2048 steps.
- BLHeli_S supports very high motor Speeds. A BB1 MCU will support 350k erpm, and the limit of the BB2 is not yet known, so the code is set to
limit at 500k erpm.
- BLHeli_S supports regular 1-2ms input signal, as well as Oneshot125, Oneshot42 and Multishot. Autodetected when the ESC sees an input signal.