Loading... Please wait...
Click the image above to see a larger version
  • AIR3 Gel Mounted IMU - AIR3 PARIS Sirius™Air HERO•32 F3 SPI - BetaFlight - Sbus - damped Drone autopilot - flight Controller board
  • Gel Mounted IMU - AIR3 PARIS Sirius™Air HERO•32 F3 SPI - BetaFlight - Sbus - damped Drone autopilot - flight Controller board AU NZ USA
  • replacement upgrade part for Air v2 owners - AIR3 PARIS Sirius™Air HERO•32 F3 SPI - BetaFlight - Sbus - damped Drone autopilot - flight Controller board
  • AIR3 PARIS Sirius™Air HERO•32 F3 SPI - BetaFlight - Sbus - damped Drone autopilot - flight Controller board
  •  AIR3 AirHeroF3 - For small drones like KNIFE240 the AIR3 can be mounted sideways on 10mm Standoffs - to allow the USB port to exit on the right hand side - keep signal wires TWISTED with GND wire to ensure no signal noise ; then just set YAW offset to 270° in the UI
  • AIR3 FULL METAL JACKET vibration isolation - AIR3 PARIS Sirius™Air HERO•32 F3 SPI - BetaFlight - Sbus - damped Drone autopilot - flight Controller board
  • AIR3 Polycarbonate Case - Vibration reduction - AIR3 PARIS Sirius™Air HERO•32 F3 SPI - BetaFlight - Sbus - damped Drone autopilot - flight Controller board
  • AIR3 - family - 3 levels of vibration reduction - AIR3 PARIS Sirius™Air HERO•32 F3 SPI - BetaFlight - Sbus - damped Drone autopilot - flight Controller board
  • AIR3 BetaFlight BF 3.1.0 - with OSD on M5 & M6 ; or iNav QuadX with I2C MAG/Compass on M5/M6 -M8N GPS in flex port
  • BetaFlight Only
  • BetaFlight only
  • BetaFlight only
  • CF iNav with GPS
  • CF iNav with GPS
  • For and Receiver 6Ch or more - the wiring sequence colours are shown here - Spektrum for example
  • Paris_Sirius_AIR3_iNav_I2C_MAG_Pins_wiring
  • Paris_Sirius_AIR3_iNav_Motor_Numbers
  • BetaFlight UI for Sirius™ AIR3 F3 spi -  configured Quad-X in this instance
  • BetaFlight UI for Sirius™ AIR3 F3 spi -  you can setup all your Aux channels as you might refer - and test them
  • BetaFlight UI for Sirius™ AIR3 F3 spi -  Check your RC Rx outputs as seen by the flight controller live
  • BetaFlight UI for Sirius™ AIR3 F3 spi -  PIds
  • AIR3 BetaFlight - features 3 UARTS Ports.  UART1 is shared by USB & DATA Telemetry ; UART2 is usually used for SBus Rx ; UART3 is reserved for Flex Port or GPS

AIR3 PARIS Sirius™AirHERO32 F3 SPI - BetaFlight - Sbus - damped Drone autopilot - flight Controller board

Shipping Weight:
95.00 Grams
Stock Remaining:

Product Description

See the newest PARIS Sirius™  2017 Air F3 iNav HERE


3 levels of Vibration Isolation - Air3 Air HERO•32 F3 with SPi fast databus - an original design - for drones - BetaFlight/CleanFLight
Sirius™ AIR3 - BetaFlight F3 SPi board -  PARIS Sirius™ AIR HERO•32 F3 - the third evolution of the only controller with GEL+inertial damping and 100% SPI tech since 2013-2016 - Software pre-installed  BetaFlight (3.1.7)  tuned for Scarab Knife drones - choose your mounting options from naked(upgrade an existing cased AIR)/30.5mm PCB damped mount/Polycarbonate damped mount/Full Metal jacket inertial dampened against drone vibration on larger drones  -
  AIR3 Features a 32 bit F3 SPI STM ARM based CPU (What is SPI? SPI = a much faster sensor bus - Hero 32 SPI gyro/acc/baro data is 10x faster than other i2c f3 designs BetaFlight makes freestyle Acrobatics much easier to fly smoothly and has very positive lock for 4 point rolls , flips or inverted moves -  uses the BetaFlight CHROME interface UI -  easy plug-n-play interface (free Google Chrome extension)  paris-air-32-4158.jpg

For noob Q & A questions - see bottom of this page

Whats New in the AIR HERO*32 F3 BetaFlight?  

  • paris-air-32-4156b.jpgAir HERO•32 F3 is a faster ARM Cortex CPU with an inbuilt maths co-processor used for GPS-Nav and all sensors GYRO/ACC/BARO on AIR3 are connected by SPI bus - SPI is very rare tech with no data bottlenecks as experienced by 95% of other f1 and f3 designs which still use i2c  - Air Hero3 can run at full 8k/8k on SPI 3.0.0 BF Acc off ; or 8K/2k ACC On 3.1.7
  • Choice of 3 mounts - ALL FEATURE vibration damping - we developed ths in 2013 on AIR - on AIR2 and again on AIR3
  • Hero AIR3 supports DShot - Yes tested 100% compatible with DShot - code files for DShot AIR3 Firmware Nov 2016 download HERE Air3+CarbonBee30a ESCs as used on Knife240
  • Hero•32F3 supports C-PPM receivers like D4R-II, yes at Pin 4 (same as S.Bus)
  • Hero•32F3 Futaba and Taranis FrSky SBus - Yes at Pin 6 (for Taranis you will need to set travel limit to 80%)  set ports tab UART2 = Serial Rx SAVE ; Configuration tab, Receiver Mode = Rx_Serial ; Serial Receiver provider = SBus ; Save
    Hero•32F3 supports Spektrum™ Rx - yes- Sat Rx see photo right  -  it also supports any 6 Wire 6 Ch Rx - choose 6 wires Rx
  • Hero•32F3 Supports Quads - yes BF is optimised for Quads ; paris-air-32-4162.jpg
  • Hero•32F3 Supports Hexii - CF yes M5 and M6 for motors 5 and 6
  • Hero•32F3 supports tricopters - CF yes - servo on M4 - then motors pin 1 2 3
  • Hero•32F3 Supports Planes/Wing -  yes iNAV Version is HERE
  • Flex Port - UART3 - is for iNAV GPS serial M8N - see iNAV Quad-X version is HERE
  • Compass Port i2c = SCL=M5 ; SCA=M6 for iNAv only 
  • Hero•32 F3 supports any 6 Ch RC receiver , yes - mini-molex SBus cable or 6 pins PWM cable is supplied in this kit ; select at top right

Question - What's the idea of the Hero•32 F3 metal case ? We have added mass - mass for an IMU to be isolated from vibrations or sensor "noise" - all of the cases in progressive order of magnitude resists the vibrations coming from the motors/props etc - so the dual function of GEL and IMU damping and crash protection are combined. The case is mounted by our special Gell tape and not bolted to the airframe.

Question - Hero•32F3 GPS? Answer - Yes hardware is 100% iNav/GPS ready - including an SPI BARO 

Hero•32 F3 Specs


  • Full SPI Databus - GYRO/ACC/BARO - all SPi(BF 3.1.7 spi Baro code for AIR3 HERE - after flashing activate BARO in UI)
  • Inertial damping - engineered to resist and reduce noise
  • Weight 3.6g pcb without 90° connectors  
  • size 21mmx36mmx7mm - no pins - for direct diy soldering to reduce risk - see photos above on How-to
  • size of inertial damping case external 46*27*20mm if used


Hero•32 F3 BetaFlightIncludes

  • PARIS Sirius AIR HERO*32 F3 Flight Controller - BetaFlight firmware installed and tuned for Sbus TEAR Knife 270 size.  Choose your level of IMU vibration damping - above - right
  • Plug-n-play ....F3 BetaFlight ... Pre-Configured and tuned for a Mini QuadX such as Knife  - just set up your Radio and connect Sbusf Rx such as X4R - then verify sticks in UI - Channel mapping - check the photos on this page for Receiver connection

notes ; DOWNLOAD & CONNECT : To upload code to AIR3 in BF click the switch for "manual baud rate=ON" set to 256000 for the any flashing 

Question ; Does Air3 work with DShot? - Yes - Dshot enabled firmware for AIR3 Here uses 115200 connect speed over USB. We saw the biggest improvement with MULTISHOT and we therefor recommend Multishot with BLHEli - but feel free to use DShot if you like it.



  • Excludes 6Ch Spektrum style RC wire sold HERE
  • ! Be sure to keep your Quad STILL/MOTIONLESS/LEVEL for the first 5 secs after powering up the main LiPo/AIR HERO*32 - otherwise the gyro won't calibrate correctly - during this process the green&blue LED are on - after gyro calibration is completed the blue LED will go off -  If the RED LED is on this means you are in Horizon mode - remember that FPV pilot fly in ACRO mode - ACRO is the HERO mode - we only use Horizon for photography work (hovering still) or noobs use it -but if you use horizon too  much your skills will start to fail and disappear.  Always do a few batteries in HERO (ACRO) mode with your HERO•32
  • excludes USB cable 2m (USB-> USB micro required sold HERE)
  • Support - RCGroups PARIS AIR Hero•32 forum here  rcgroups-support.jpg    <--- Support ; or FaceBook Support Group HERE
  • Excludes setup on USB/PC/Mac by user - it's easy - see below
  • Excludes pilot training - we recommend start to learn with the use of a flight SIMwarning-multiwiicopter-safety-symbols.jpg
  • SAFETY RISK WARNING Excludes RC setup and failsafe setup - Risk vs Safety to others must be considered fully by the pilot  in advance of your first flight - You must decide what's going to be your failsafe pre-set setup and program the Rx with Failsafe settings - this is something THE PILOT does himself - FYI failsafe by Futaba/Spektrum/Taranis/FrSky is stored in the receiver (the BetaFlight fa failsafe should never be used for one of these advance Tx/Rx setups - it is for ultra cheap cloneking Rx with no failsafe - So if you have a good brand of Radio like Taranis then we recommend you pre-set the failsafe in the Rx itself for all controls and mode switches) - NEVER fly out of range at high altitude - never fly out of sight LOS rule is very clear - you must keep sight of your Quad at all times - after you hit a tree branch (i.e. high risk flying, doing something beyond your level - we recommend you do NOT copy advanced pilots videos if you are a noob) - so after a crash/impact you have to cut & disarm the motors by RC as soon as it's DOWN - this means even if you cannot see your Quad, you may still be sending RC signals to drive the props and motors - this can lead to a burnt ESC/motors situation with noobs who have not thought out whats going to happen if they leave their throttle high or have their failsafe high.  We recommend you immediately set throttle to Zero and disarm within seconds after a crash touchdown - NOTE this - but, it's your decision as the pilot what Failsafe throttle setting and mode you want and what kind of flying/risks you are prepared to take both to yourself, others and finally of least importance but something to consider, your equipment (ESCs still commanded to turn after impact) - We recommend you rehearse your emergency procedures in advance - copter down procedure, and drill this - so when you have a crash you know what to do, exactly.  We Strongly recommend you program a failsafe into your Rx for slow descent 1200-1300uSec (depending on props) in Horizon Mode - then bind/set failsafe - this reduces risk to others - always fly at least 50m away from people or property of others such as cars etc 


HERO*32 F3 Downloads

HERO*32 F3 Configuration 
we have pre-configured PIDS, Yaw alignment, motors stop on ARM, Channel mapping for Taranis Sbus TEAR - however as we don't know what type of RC Rx you want to use - thats something you have to do - select the correct Rx - connect it correctly (see photos above) then ensure your mid points are 1500 and your end points are <1095 ; more than 1905 ;; and you have to make decisions about failsafe and then set your RX failsafe itself too - so you MUST read the steps below - some of the things will already be set when you go to check them.  DO NOT press the button called "RESET SETTINGS" it will wipe all of the pre-configured stuff we have done for you. so in summary - ALL THIS STUFF BELOW IS ALREADY DONE for you except the usb driver on your PC

Also make sure your ESC are running BLHeli 16.1 or newer !  We now ship ESCs with MultiShot enabled - it's great 

HERO*32 F3 Engine numbers - see Photos above - note these are DIFFERENT to older Airv2 or original Hero - be sure to use those above

ESC are connected with the control wire facing up (yellow or white at the top) - do NOT reverse these wires - NOTE you MUST use the below engine number mapping - NOT the GUI mapping


HERO*32 F3 CLI commands


One of the most useful CLI commands is 

  • set

this gives you a report on all setting stored in the PARIS AIR Hero•32 F3


Noob Questions

I cannot see any comm ports in BetaFlight? - Quit BetaFlight ; disconnect USB ; wait 2 secs ; re-connect USB ; re-start BF and check the comm port - this helps a lot as BF can hang.  Next,  have you loaded/installed the Silabs driver ? - see downloads above - or it's possible you are running an older BF2.4 or 2.6 if you have this problem ; some earlier versions ran a higher speed 500,000 connect  ; try to connect with BF 2.4. or 2.6 - set USB to 500,000 and select SLAB_USBtoUART


Be Aware - However this was reversed and later versions of BF such as the current 3.1.7 connect at 115200

I am obsessed with loading new firmware when i buy things - Should i wipe the HERO32F3 and install the latest firmware online?  NO, NO, NO ! -  the "Beta" in betaFlight is there for a reason - daily updates are "bleeding Edge" untested beta - So in 99.9% of cases if you try to install the newest beta firmware (before flying) you will go backwards in terms of RISK  to your drone / product -  Your AIR3 HERO•32 has already been Flashed/tested by us at shipping date,  with the latest STABLE version of BF firmware.  If you want to risk upgrades - ALWAYS FIRST do a CLi "DUMP" and save that .txt file. That way if you mess it up - you have a way to roll back ....  However as a rule we STRONGLY recommend to fly first using the firmware "as supplied" -   naturally you must still do all your checks and RC setup.

My AIR3 HERO*32 flops around and won't fly?  Do not move it during the first 5 secs after powering up the main LiPo - during the first few seconds the GYRO is calibrating itself

Should i solder pins or solder ESC direct ? Answer = Risk - so soldering is much safer as it removes the risk of intermittent or failed contact of a push-connector - we recommend soldering the wires.  Direct soldering of ESC control wires reduces risk and is used by pro-pilots to crash harden a Scarab. On Scarab Knife 240 if you are doing the direct solder upgrade hack, we recommend you also change the 5mm standoffs to 10mm nylon standoffs ; cut away the pins and rotate the AIR32 by 90° to allow the USB to exit to the right side at the same time. Be sure to keep all your ESC control wires well twisted (a control wire twisted tightly with a GND wire reduces noise being injected into that wire) ; route ESC control wires clear of EMI/RFI as per these photos ; use copper shielding to future improve Video signals.



All my Motors Chirp as soon as i connect the main LiPo and keep chirping?  Motor Chirp is a safety warning that the RC Tx/Rx signal is dead ; or the THRO signal is NOT <1050 uSec - set your end points to 1090/1500/1910 and if using MULTI-SHOT make sure min command and min throttle are at least 90 points different ie 970 vs 1089 ; also make absolutely sure when the left stick is at the bottom (towards you) that the UI shows throttle channel is <1090 (you may need to reverse the Ch if the throttle UI bar is high >1800 when you check this) - if your motors only chirp after 2 mins - that normal for BEACON or lost model chirping.

When i increase throttle nothing happens? For safety make sure ALL your props are OFF - then learn the ARM and Disarm stick commands below

How do i make sure i am in Acro mode? Go to the UI MODES tab and make sure you mode switch (usually SB) is in the position for all modes Red - a green mode means that mode such as HORIZON or ANGLE(atti) are active - 

My HERO*32 is twitching in the hover - This is very rare now with our new props and CarbonBird motors and GEL DAMPING design of AIR3  ; but - 1) Balance your motors and your Balance/check your props fully - lazy pilots don't get smooth Quads - suck it up and balance your props while watching southpark  2) ensure your looptime 8k/4k  see above  3) Check your PIDs are as per the above photo above

My HERO*32 won't connect - load the USB drivers above - shut down - restart your PC

My HERO*32 motors all start at different times - yourRC centres are not at 1500 - use the BETA Flight GUI to trim your RC Tx to 1500 - Sbus makes this a LOT easier and more accurate

My Receiver has no Power on USB?  - The Receiver shares the DC rail  powered by USB. but the ESCs will NOT be powered by USB - to activate ESCs - remove props and connect the main LiPo to the PDB

I tried to use my old MuliWiiConf - now various things are messed up?   Do NOT ever use 23 MultiWiiConf GUI code as it's out of date compared to BetaFlight - if you accidentally invoke multiwiiConf java window - you must backup your settings - reload the code from scratch via BetaFlight and restore those settings - or send it back for a paid firmware fix.

I want to connect a MinumOSD to my AIR3 ?  Requires you upload LOCAL code (v3.1.7 or later) to AIR3;  in BF click the switch for "manual baud rate=ON" set to 256000 for the flashing phase ;  select the latest AIR3 BF 3.1.7 Firmware for Download ; then Use the R & T pins  (Telem OSD Receive/Transmit + GND and 5v from the back pins R->T ; T->R )  then ; FOR OSD enable UART1 at 115200 as a msp in the PORTS tab of BetaFlight (new BF 3.1.7 will default to set all UART at 500,000 and MinumOSD requires UART1 set to 115200 only) ; and then enable telemetry in the Configuration tab, save. Be aware that OSD and USB both share UART Port 1 so if you want to go back into USB to alter PIDs then disconnect Rx/Tx temporarily  - Hero•32 F3 the 5.0v Vcc must be connected to 4 Quad ESC centre pins M1-4 as the other 2 pins (below M5&6) are now used for OSD data output (see blue/green circles  below).

air3-inav-i2c-mag-pins-wiring.jpg paris-AIR3-iosd-with-gps-co-ordinates shown on. Scarab OSD  

I want to connect RGB LED strips to my PARIS Hero•32? You must be running either Sbus or CPPM Rx - then use Pin RC5(blue wire port) as the signal wire - RGB Leds use 5v, GND and this pin - then connect them in series - in->out->in_>out etc

I am getting glitches/flips at random with my Hero•32 naze and my FrSky X4R (D4RII) - Why?  Signal injection interference RFI - always twist any signal wire with a GND wire to reduce interference - also It's critical to keep any RC receiver Rx away from ESCs by at least 50-80mm - this can be tricky on a mini - so if too close, we recommend wrapping the Rx in heat shrink - then Copper tape as a RF shield, then adding a final layer of heatshrink to ensure no short circuit.  Then still do your best to keep it 35mm away from ESCs, if you can do that

I want to add extra i2c stuff like I2C MAG for iNav Flex port? How?   For AIR3 the Flexport = Serial GPS port in iNav CF ; For  BetaFlight i2c is disabled n/a and motors 5&6 for Hexii are enabled ; for iNav i2c Mag Compass SCL/SCA are on M5/M6 top row pins - Quad Only - (above Rx/Tx which are Telem OSD pins)

I want to add a serial GPS and code it for Aeroplanes - RTH etc - This option called iNAV is HERE

How do i add a Lost model Alarm (LMA) buzzer or LED strip ? For a PARIS Sirius AIR Hero•32 bit buzzer the pad internally marker "LED" is a GND trigger for up to 1A. Can also be used for a buzzer or LED strip lights etc ...... To trigger a 5v buzzer connect buzzer -ve GND ->LED ; connect 5v + to one of the centre 5v rail pins.  this applies to a std piezo 5v buzzer with two wires Red/Black  - 

PWM LMA Buzzer or a FPV Camera-tilt servo ( note never disconnect or connect a servo with live 5v power ! - you may permanently damage the Hero32 outputs/CPU - POWER OFF FIRST) - For a Pilot activated or Failsafe activated option on PARIS Sirius AIR Hero•32 bit buzzer - ie a more sophisticated LMA using a PWM 3-wire buzzer and C-PPM Rx setup these go active >1500uSecs - so you can pass Aux1->2 to Rx RC 5&6 -  ideally Aux 2 would be passed to RC6 - the last wire Purple would be connected to the buzzer white wire); and then GND->GND ; +ve to 5v   (same for a servo tilting your FPV camera down - we removed the servo orange wire and connected it to RC6 purple wire and then plugged the servo connector (now only had red/black)  to M1 to provide 5v power)

  • Then use the CLI command set gimbal_flags=4

 air-hero32-naze-pass-thru-tilt-servo-4582.jpg  hero32-naze-lost-model-alarm-lma.jpg


Question = What are the stick commands for CleanFlight?  For Mode 2 (throttle on left) use these stick combinations - be aware that the stick must be held in this position for approx 1 sec.  For example you can see Arming/Dis-arming stick commands below (hold for 1 sec)



Question - For the 6 wires Receiver (Rx) cable what are the inputs ?  answer = Most Rx have the THROttle on Channel 1 - but futaba (DevO) have throttle on Ch3 - some radio makers call channel 5 and channel 6 by old outdated fixed wing names like Gear or flaps)

so for Devotion ( = futaba) the wires have THRO = white on Ch3 -then the same sequence as the other end

Yellow = Elevator = Ch 1
Orange= Aileron = Ch 2
White = Throttle = Ch 3
Green = Rudder = Ch 4
Blue = Gear = Ch 5
Purple = Aux 1 = Ch 6

For Taranis / JR / Spektrum - the wires have the same colour sequence at both ends of the cable Rx->PARIS

White = Throttle = Ch 1
Yellow = Elevator = Ch 2
Orange= Aileron = Ch 3
Green = Rudder = Ch 4
Blue = Aux1 = Ch 5 (Spektrum call this Ch GEAR)
Purple = Aux 2 = Ch 6  (Spektrum Call this Ch Aux1)




Write your own product review

Product Reviews

  1. AIR3 Reliable Aussie Tech that I Trust 100%

    Posted by Tom crashtestDummy on 11th Jan 2017

    The Paris Air3 is my go to flight controller. Having used nearly every flight controller on the drone market, I keep coming back to this AIR3 as it has GEL DAMPING and does all the things I want, with reliability I have yet to find in any other flight controller.
    AIR3's compact size helps with tight builds and has all the features you need for a mini quad. I combine this with the mini-Andromeda OSD-90 PDB for nearly all my builds. The fact that it comes with the latest Betaflight and smooth flyable pids loaded onto it takes the guess work out of setup your quad. Highly recommended!

  2. Evolution of my most used FC

    Posted by Damien Pitt on 27th Sep 2016

    The Air3 board and is typical multiwiicopter stuff (that is to say, it just works, no fuffing about). Soldered some pins on (I usually avoid pins but I only have a chisel tip so direct soldering was starting to take it's toll on some other components with heat on the PCB and I seem to find an excuse to pull quads down and rebuild every week), connected ESC's, plugged in RX. Checked the BF software, everything about the Air3 was already done, BF 3.0 preloaded, everything to run Sbus checked, etc etc, so I just plugged it all in and went for a fly.

    Maidened, smooth as silk. No PID adjustments or tuning yet, just put it in the air and it flew brilliantly.

    I still think when you look at the flight 'feel,' I don't believe there's any real 'omg' revelation about feeling more or less locked in in regular flight compared to a standard F1 based board (though if you often read forums people talk about the need to go to F3 boards like F1 practically can't be flown these days, I have to remind myself that all my F1 based boards could wobble out of the sky at any moment) but what I have found is that at the hard edge of manoeuvres is where you see the benefit of those really fast fine adjustments so if you do like to fly hard, you will get these benefits of the F3 at the extreme limits, just don't expect it to make you go from average joe to absolute hero, the only way there is via the fleshy thing attached to the transmitter (that's you, and lots of practice).

    Of note, it still uses the 'gasp' 6500 gyro, the one everyone says is an issue but to be honest having used multiple Paris boards using that gyro it's always been a hardware issue, you can't strap something down direct to an object that has inherent vibration and not expect issues, the whole thing reminds me of a dog chasing it's tail; hard mount an FC, find hardware solution picks up hardware problem, spend weeks chasing solution in software. It's basically taking the sensitivity of the gyro and then saying 'lets just dumb down the s*** out of it till it ignores the vibrations'

    Anyway yeh, I had done a lot of research on FC's, looked at FC / PDB integrated units, this that and every other combination; never really found anything that didn't have some form of issue in one shape or another so I stuck with what I know having never had a Paris Air or Paris 32 play up on me and yeh, no issues.

    So if you are in the market for a new FC do you go with this (the new F3 based board) or the older F1 boards? The F1 is still a very capable board and I have used them now for the longest period without issue; but going forward, get yourself the F3, there's really no down side to it.

Currency conversion