Loading... Please wait...
Click the image above to see a larger version
  • PARIS v5r3 Mega + with onboard OSD + GPS - Open Source AutoPilot - Mac/PC
  • OSD - On screen display included - PARIS v5r3 Mega + with onboard OSD + GPS - Open Source AutoPilot - Mac/PC
  • Receiver connection sequence for Taranis - TAER - PARIS v5r3 Mega + with onboard OSD + GPS - Open Source AutoPilot - Mac/PC
  • Receiver connection sequence - Spektrum - PARIS v5r3 Mega + with onboard OSD + GPS - Open Source AutoPilot - Mac/PC
  • PARIS v5r3 Mega + with onboard OSD + GPS - Open Source AutoPilot - Mac/PC AU NZ USA
  • direct connection to oLED, HiVis daylight LED for LOS , RGB LED ring for modes and compass "N" - PARIS v5r3 Mega + with onboard OSD + GPS - Open Source AutoPilot - Mac/PC
  • actual iOSD screen of PARIS v5r3 - PARIS v5r3 Mega + with onboard OSD + GPS - Open Source AutoPilot - Mac/PC
  • mounted - PARIS v5r3 Mega + with onboard OSD + GPS - Open Source AutoPilot - Mac/PC
  • mounted under rain dome PARIS v5r3 Mega + with onboard OSD + GPS - Open Source AutoPilot - Mac/PC
  • Enter your area MAG declination in the GUI - settings TAB - save
  • UI - fully functional UI for the AUTOPILOT - PARIS v5r3 Mega + with onboard OSD + GPS - Open Source AutoPilot - Mac/PC
  • effective 22 Jun 2015 - GPS/MAG is combined into v2r1 GPS - Serial/I2C GPS
  • effective 22 Jun 2015 - GPS/MAG is combined into v2r1 GPS - Serial/I2C GPS
  • PARIS v5r3 flight controller and GPS RTH + OSD
  • PID settings for WING - PARIS v5r3 flight controller and GPS RTH + OSD

PARIS v5r3 Mega + with full OSD + GPS - MultiWii board - Mac/PC

Shipping Weight:
156.00 Grams
Stock Remaining:

Product Description

See the newest PARIS Sirius™  2017 Air F3 iNav HERE

USD139 - on sale USD89  !   while stocks last - PARIS Sirius™ v5r3 Mega iOSD +GPS is the trusted v5r3 integrates with Andromeda v3r3 oLED/LEDRing in hardware and also features new updated iOSD functions with Scarab OSD. The V5r3 has a dedicated gel mounted IMU in a metal case ! - it offers a single connection to Andromeda v3r3 LEDRing and an oLED with no fuss - Don't be fooled by the low price of the v5r3 - it's a sirius controller for big multicopters including bigger more expensive OctaCopters  -  This autopilot offers open source code base and a "non-obstructive control" to film-makers giving 100% pilot feel - control yet offers the FULL feature set of assist modes like self levelling, GPS hold and GPS return with full OSD onboard. The PARIS v5r3 MegaOSD features multiWii code base and "Hero" smoothest gyro mode film making FPV 100% control without fear of flip-outs or fly-aways   - PARISv5r3 leaves all other autopilots in the dust with their tragic solder to motherboard sensors being near unusable.  At the heart of the PARISv5r3 is a metal encased IMU riding on a special Gel isolator - Most significant for PARIS v5r3 Mega iOSD.

paris-v5r3-iosd-with-gps-co-ordinates.jpg  andromeda-v3r3-orientation-ring.jpg
Built-in iOSD video overlay data - included                                       Optional i2c datalinked RGB LED + Daylight hi-VisLED + oLED +12v regs

For Q & A nood or Questions/answers - see below - this page ; or use search page function and enter keyword (control F)

Features paris-bt4-ble-ui-link.jpg

  1. Ultra Reliable with full RTH return home and instant self level - not prone to delayed flip-of-death - the software does not cloak issues - if there is a problem such as vibration it will be evident immediate you take off - not 5 mins later when it does a huge shenzhen naza flip
  2. Mega CPU Atmel 2560 - OPEN source code - lots of memory  - practical,clean layout with onboard /remote IMU gel mount (allows the IMU to remain in the centre and locate the PARIS off-centre)
  3. On-board OSD !  hardware overlay with built in heatsink - pre-installed software - iOSD running at 5v - if needed - connects to PC Win7/8 or to Apple Mac OSX Mavericks using the JAVA GUI interface - but not essential - Simply connect your 5/12v FPV camera with matching 5/12v FPV Tx - setup can be done on your ground station using Tx sticks, while dis-armed (see below) - and Fly
  4. Fast and larger Serial GPS - uBlox 
  5. Connects to PC Win7/8 or to Apple Mac OSX Mavericks using the JAVA GUI interface via USB
  6. Separate gel isolated IMU - Sensors - Gyro = 3050 , Acc = Bosch 280 - can be remote located to the aircraft C of G - Why do we use the 3050? - on paper it seems to be older? - but for real pilots doing real flying with 600-1000mm class multicopters using lower harmonic resonance  associated with bigger props - the 3050 is a way better/smoother gyro - highly resistant multicopter vibrations and resonances - hence the reason we like it (a 6050 is more suited to cell phones or devices with very small very high rpm like a 250mm quad only)
  7. super sensative Barometer MS5611 bottom-mounted to minimise light errors - offers a 3 fold improvement over PARIS v4r6 baro accuracy
  8. 1 x dedicated I2C 5 pin Micro JST input ( for Andromeda Core v3r3 = oLED / LED Ring)
  9. 2 x LV I2C 4 Pin Micro JST inputs (for IMU & MAG-Compass)
  10. 4 x function LEDs (pins 30,31,32 and 13) - 9 LED's in total including the GPS 
  11. 4 Serial buses with separate Molex/inputs (Serial 0=USB/Bluetooth RS232) (Serial 2=GPS Serial) (serial 3 = OSD) (Serial 1=PPMSUM C-PPM input on pin 19 - servo side) - also we have designed the GPS and the OSD plugs to be swapped over if necessary when running other non std software.
  12. All pins A0->A7 have been brought out to allow further expert Customisation with code for expert coders - such as battery monitor via A0 (this is different to OSD Voltage which we prefer)
  13. iOSD inputs x 3 kinds - OSD Voltage - OSD Amps sensing device -  FrSky  Rssi (max voltage 1.1v check it first)- these feature pre-installed inline 1K resistors and divers for 4S so that the iOSD will give correct voltages on 4s and function with FrSky Rx TFR4 that have rssi output. Please note that to access Rssi /volts/amps you need additional compatible equipment/wiring or soldering - NOT included.
  14. RS232 Bluetooth molex connector Micro JST 4 pin (USB and Bluetooth cannot be used together at the same time - disconnect Bluetooth when using USB)
  15. Open source MultiWii code installed v2.3 - Download GUI 2.3 HERE - If you want to modify something - you can... unlike other products in the market with ZERO flexibility.frsky-sbus-inverter-paris-v5-available.jpg
  16. Can also be used with a totally different codebase - a special version of ArduCopter waypoint Navigation called Mega Pirates NG 3.0.1 software HERE - the PCB has been designed to allow instant switching of the GPS and the OSD to match MEGAPirates Nav code and pin assignment - for expert coders - the How-to-install Magepirates is listed below on this page - see Question 12 at the bottom of this page
  17. 8 RC Channel inputs - RC Plus Aux1 & Aux 2 Micro JST - > RC Receiver plugs - 190mm cable - works with any RC Receiver - if using C-PPM PPM-SUM this can be disconnected as the Serial pin 19 pins are on the ESC side
  18. 8 Engine outputs - Tricopter, Avatar, Quad, Hexi, YSix or Octas (pins 3,5,6,2,7,8,9,10) and 2 servos at the same time (pins 11,12) and
  19. 3 Servo gimbal outputs (For a servo camera gimbal tilt AUX 3, or MultiWii camera gimbal tilt on AUX4 for example) use Pin 44= camera Pitch tilt, Pin 45=Camera Roll, and use Pin 46= a Camera shutter servo press or servo drop function or open a  Parachute, or LMA lost model alarm on Pin 46) - you can use the GUI to set Camera tilt down via AUX3 Ch7 or AUX5 (ch9) if you have Sbus connected on Pin19 -  to tilt the camera down with the right slider of your Taranis X8R - see HERE in Tech FAQ
  20. MultiWii software 2.3 Arduino Open source software by AlexinParis - unlimited control and access to the codebase (make sure to use new GUI 2.3)
  21. Split DC 5.0v bus for noise filtering.  Optional - By splitting the DC bus into two sections noise generated by ESCs and servos is not transferred to the CPU/Sensor bus which is supplied by a dedicated 5v BEC.  simply un-solder the noise bridge if required. Be sure not to use a switching BEC which may conflict with i2C.  The preferred system is a linear BEC.
  22. LLC and hardware pull-up options on the HV bus - something we pioneered long ago
  23. Andromeda triggering via GND via mosfet pin on the Paris v5.
  24. No soldering - finished - tested and pre-programmed ! (Soldering is required for expert functions such as Rssi)
  25. Works with 12 multicopter types = Bi-copter, Tricopter, Avatar, Quad+, Quad X, Y4 Hex+, Hex X , Hex-H, YSiix or X-8 or Octa+ or Octa X - Plug-n-play (not plug n Fly)  works with any PPM 5Ch or more RC Receiver (almost every radio made in last 10 years is PPM) including   FrSky®, Futaba®, JR®, Spektrum®, Hitec Aurora® or Graupner®,  - Requires that your Transmitter is first calibrated in the GUI to output accurate uSec values of 1095/1500/1905 on all 5 Channels - works best with 8 Ch Receiver or PPM-SUM Rx (CPPM FrSky)  to access Aux 3(ch 7) and Aux 4(ch 8) - Works with mode 2 or mode 1 transmitters
  26. 2mm FR-4 mil-spec board, aviation grade - we make the toughest boards out there - by far
  27. POWER consumption - When working normally correctly the entire PARIS v5r3/Video Chip/Sensors/GPS draws 0.22amps @ 5v - the sensors should all remain at room temperature - only the video chip produces heat disapatted thru the upper heatsink (under the IMU) - if any sensor becomes hot >40°C then power down PARIS - disconnect the sensors and do not fly - the sensor will only produce heat if damaged in a crash - shorted)
  28. thick copper 105um for strong solder joints,vibration and crash survival
  29. 72mm diameter board - drill holes are 45mm Square - some holes are omitted due to component placement
  30. RoHS lead free - GREEN PRODUCT
  31. Designed in Australia and born for flight by experienced MultiwiiCopter FPV pilots from around the world within our MultiWii Scarab community - MultiWiiCopter.com are genuine Founders/pioneers of the multicopter movement started in Dec 2010 - with the release of the first PARIS v1 autopilot exactly 3 years ago - exporting worldwide
  32. Manufactured by us, Assembled in AU by us.  Not available on any other website.


What modes does PARIS v5 have? The default mode is acro HERO or manual mode (gyros only ; sometimes called ACRO mode or Manual mode or Pilot Mode) - Additional modes can be activated to aid the pilot to hover if he needs to stop for sec - These are setup using the GUI check boxes - or use the supplied default ones as this is already done for you when you order

HERO - Gyros only mode - sometimes called full-manual mode or acro mode - in this mode the gyros prevent disturbance from wind and turbulence but do NOT interfere with pilot inputs - its a crisp and responsive mode - absolute best mode for amazing video flying.  Way way better than dji manual mode which is sloppy - the PARIS v5r3 has a crisp locked-in feel.
ARM - we recommend NOT arm by switch unless your running a big Hunter Triikopta  - reason - it's a waste of 4 possible switch positions other than off - if you have 2*3 ways switches - use them for other stuff below
ANGLE - this activates the Accelerometer - self levelling mode - (was called LEVEL or ACC before and is called Atti by dji) - its a beginner mode used for hovering - we don't recommend you Fly in this mode - its designed for hovering directly above your position - where it's otherwise difficult to see small attitude changes.  Its useful for FPV take off and land IF your experienced - do not use this for your first noob maiden take off as it confuse you - the acc is sensitive to 0.1° tilt and will rev the props on the downhill side like buggery until its gets its 0.1° offset sorted - its a required mode for RTH

HORIZON - this is a cool new multiWii mode - stable mode - so when the cyclic stick is near the centre the Acc is activated (self levelling) - but when you want to fly fast forward or even do Acrobatic flips and you push the cyclic controls toward the edges - then its gyros only - love this new mode
BARO - First set the aircraft in the hover at 50% throttle - then engage BARO switch - the autopilot will power the motors up/down to hold the Altitude based on barometric pressure - Do NOT take off and fly around on BARO - on the v5 the Baro sensor is already bottom-mounted - if exposed to airflow (no dome is used) then cover the BARO with black felt - this prevent erroneous barometric pressure waves from speed or wind entering the BARO.  You cannot ARM with BARO on - this is becuase baro can only be switch on once you are hovering or cruising at 50% throttle.
MAG - Compass or heading locks yaw in the hover - be sure you have 1500 setup as the RC Tx Rudder ! check your GUI - use manual tilt to trim residual yaw out in early test flights - then when the rudder or yaw stick is centred - engage MAG - this will lock the heading.  We don't recommend flying around with MAG on - reason - MAG will lock out if bank angle exceeds 20°.  Mag is useful for doing towering climbs or descents where you are flat - and trying to shoot facing one direction - be sure to tune your airframe (by engine inclination) so you have zero latent yaw. 
HEADFREE - this requires you mount the MAG(Compass) away from all magnetic interference using an analogue compass to check it - in small aircraft the centre (Sirius) is fine - but in larger craft you will need to use the remote GPS/Mag and situate it well outside any RMI - check for magnetic disturbance with an analogue MAG first  - Once activated the aircraft uses the compass offset from ARM/TakeOff heading to equally offset the cyclic controls - so for example you activate HEADFREE then you take off and turn the Scarab to face yourself the left cyclic will still bank to your left - even though the aircraft has rotated 180° - be sure not to turn your body - i.e. stand in the same footprint thru the entire flight.
HEADADJ - allows you to re-align headfree lock position if you turn your body from the original ARMED/Take-off direction - active this switch to RESET headfree ; turn your body and have the craft face away from you ->- then immediately turn it off - the HEADFREE reference angle is now reset.
GPS HOME - very useful - a must - setup MAG/ANGLE and GPS home on the same switch position - BARO also if you prefer - then use this to fly home - will return to the position where it was last armed - does NOT control throttle so be sure to use enough power to fly/hover.  Importantly PARIS offers shared control (IMU and Pilot) during the return to home phase - it is NOT fully autonomous and does not control motors - this is a good thing as it allows the pilot to make inputs to avoid obstacles - without having to do a full manual reversion like other brands (usually ending in a massive crash).  You cannot arm with this mode on.
GPS HOLD - Sometimes called Loitering - or sky-parking - yes - if you really depend on this type of thing (noobs) then it's going to be better to run the PARIS v5 under MegaPiratesNG 3.0.1 - same hardware but different software is going to give a way different result. Under MultiWii code 2.3 make sure to save your PIDs first.  We recommend this for high altitude "parking" - use in conjunction with BARO.  Noobs sometimes believe this will "help" them fly - but in reality its like wearing floatation in a swimming pool and you will never learn to swim - or to fly - GPS hold is for the pilot to park for a few secs - while he looks at his RC warnings or timers or such data - then resume flying.  The MOST important thing for a beginner is Practice - practice makes perfect. Far more useful to noobs is the "Headfree" mode above.  Then slow wean yourself off that dependancy.  Bear in mind that FAA and CASA consider aided flight a tech-fail-risk and in the event of trouble the pilot or operators must disengage the aid and fly manually and will require you prove this skill/competency during a SC test.
OSD - allows you to toggle OSD on or OFF with a switch in flight



  • includes PARIS Sirius™ v5r3 Mega iOSD Autopilot main board -  2560 CPU - with iOSD (On screen data telemetry display) onboard - includes MS5611 Baro on lower side to protect from sunlight and shadows 
  • includes Pre-programmed with v2.3 firmware as ordered at top right - no need unless you want to modify the code !! Download 2.3 special version PARISv5r3 Sketch files (3rd Nov 2014) here
  • includes Pre-Proggrammed iOSD v1.3 (new vrsion 1.3 is effective from 17 Feb 2015)
  • includes 8 way Rx micro RC leads connector 180mm ; fits any RC Rx 
  • includes PARIS Sirius™ Navigator IMU with Gyro/Acc Can be remote mounted closer to A/c C of G
  • includes iOSD adapter cable for the FTDi (FTDi itself is sold separately)
  • includes remote GPS for Serial 2 port- uBlox Neo 6M - (effective 22 Jun GPS is v2r1) - MAG is icluded in GPS Pod - the Scarab beetle goes at the front/forwards
  • includes alternate longer IMU lead to allow remote location of PARIS and place the iMU at the C of G position
  • The PARIS forum is here - lots of helpful pilots with a common interest
  • includes Active and helpful PARIS Sirius™ forum community online 24/7 - when you get to the forum ; use to "search this thread" function , to search for key words in minutes
  • Download the correct v2.3 GUI  HERE
  • Download Mission Planner HERE and then MegaPirate FlashTool HERE - Note MegaPirates operating system then applies - not the below.
  • Excludes BLE Bluetooth module  PARIS BLE datalink - used to wirelessly link the UI to the drone up to 50m - used for checking modes, vibration levels, PIDs via Serial port (0)
  • Excludes oLED /LED Ring port is provided
  • Excludes  USB Micro lead 2 meter -red - sold HERE
  • If using servo's use a capacitor to resist brown-outs on the 5v bus  - such as Tricopter or gimbal servos - We strongly recommend 1 or 2 C1 Caps HERE (which is the same for all PARIS boards since 2010) - just connect them to any spare pins (correct polarity) on the Rx and the PARIS v5
  • Excludes FTDi 5v UART RS232 device for altering the OSD code
  • Excludes 8Ch RC Radio Receiver - We recommend Rx with Rssi functionality HERE
  • Excludes Futaba compatible FrSky TFRSP Rx for Futaba FASST+PARIS flyers here. TFRSP offer some special features for Fasst+PARIS+Alexmos+Rssi
  • Requires/Excludes connection of OSD rssi Pin for Rssi  -  The voltage sensing HV +ve wire MUST be made 100% safe - if it comes un-done and contacts the PARIS at 16.8v it will permanently damage everything - route this wire very carefully -  2 short wires and 90°/3-pins are included for choice - if used - Excludes power flow (amps) meter sender unit (future item) 
  • Excludes Dome protective dome HERE
  • Specifically excludes PC skills training - if you do not have PC skills please do NOT buy this product - the user must be able to use a PC/Mac in order to safely set & check their RC Radio settings in THE GUI 2.3. Please see the steps below and decide if you are going to struggle or cope with this type of skill set - we do not provide basic PC skills training - it is a prerequisite 
Engine Numbers
ALWAYS POWER OFF before connecting/Disconnecting Servos or ESC !!   The PARIS v5 MEGA iOSD has different engine numbers to PARIS v4.  The v5 numbers relate to the open source software pin-numbers on the CPU.  This may seem strange but it makes it much easier to customise the code without needing a special decoding chart to do so.  On the PARIS you will find the numbers printed in small white print - just inside/behind the 14 pins - be sure to take note of them before installing and relate them to the diagram below for QuadX for example pins   -  For TricopterAvatar motors 3.5.6 and Servo pin 11  ;  uBEC 44; c1 CAP 45  -  use the photos on this page as reference.  The motor directions are shown by the arrows.
Pilot Training, SMS and Risk Mitigation - This is NOT a toy - This is NOT a consumer toy device - it assume you have first used a flight simulator to develop real pilot skills (as per Airforce or Airlines method which includes using a Sim->) and that you want to be a pilot.  Use a safety management system(SMS) to reduce your risk.
  • Excludes GPS training and Drone FAA/CASA consulting services - whilst any consumer can put a GPS in a car , you will notice that you still have to drive the car yourself - more to the point, piloting an aircraft by a coupled GPS is totally different responsibility - GPS requires that the buyer fully understands GPS navigation limitations - a GPS pod is a sophisticated Navigation/Auto-pilot aid to assist a skilled and educated pilot flying LOS Ops. but only if he/she understands it first - Mis-understanding coupled GPS or GPS RTH settings and limits, will cause you to 1) loose, crash or damage your aircraft - that's your responsibility - on forums you read about GPS fly-aways and GPS Blow aways - these are specifically naive-noobs who caused their own woes by mis-adventure and ignorance - or worse  2) you possibly injure yourself or somebody else - because you don't understand Failsafe setup - so if you don't understand manual reversion ( where you de-couple the GPS and fly safe back with pilot skill in manual mode) - then don't buy a GPS equipped multicopter - period - GPS is not not Merlins magic answer to people who cannot fly - Noobs sometimes think they need GPS as some kind of crutch to walk, they imagine its a kind of laptop drone gaming experience - sorry about - but that is contrary to aviation principles and why pilots exist -in short if you need GPS - then it is NOT something for you.  If your a beginner/noob - forget GPS - develop real pilot skills - practice - fly the sim - get a small Quad and learn to to fly it manually first.
  • Excludes Safety Management Systems (SMS) consultancy and Risk Management minimisation Training courses - google these to be sure YOU KNOW what they are.
  • Excludes Arduino  training or re-flashing code is not included as its easy for the user to do themselves in 2 mins - all support is via the open source PARIS FORUM - this is a simple task to comment a sketch and upload it and you are responsible for learning how to do it  - Uses Open source MultiWii software here altered by commenting in/out code activation lines.  We assume no responsibility for the function of the source code. Buyers should satisfy themselves of the functions of the software - The software is on-going - development will continue after you purchased the PARIS Sirius - and new functions not yet know will be available.  PARIS v5r3 was optimised for code version 2.3
  • Excludes any reliance on Auto-pilot modes - You must learn to fly in ACRO hero-mode and assume responsibility for full manual by skill in 100% manual control as the pilot - no guarantee of auto-pilot of automated level mode, nor auto position holding  nor auto-navigation  is implied for the control of the aircraft.  Pilot must navigate by visual line of sight.  Pilot must hover by his skill in manual mode (ACRO) - its VERY easy - much much easier than flying a CP heli.
  • Excludes RC support for beginners who don't know anything about RC i.e. how ESC's work or what a BEC is or what Failsafe is etc... please use the forum HERE
  • Excludes a 101 course in aviation, aviation law, pilot training, prop balancing, battery management, SMS,  electronics or code commenting - Multicopters are extremely technical and NOT CONSUMER DEVICES - Drones are electronic remote aircraft and require a skilled technician/PILOT - they are only suited to people who can solve their own technical problems and like solving puzzles - if you're impatient - if you get frustrated easily - if you don't have PC skills - if you don't have time and don't read much - then we suggest YOU ARE NOT SUITED to fly drones and recommend you NOT buy a drone at all.  
  • Excludes PC or Mac support/training - excludes how to use a PC - Understanding file paths, firmware and Loading USB drivers and setting up JAVA - all are required - we don't teach this.
  • Excludes consequential loss - Warranty is strictly limited to the product itself - NEVER install props until your are fully competent and understand PARIS GUI and software functions  - Wear eye and safety protective gear PPG - If you crash your aircraft , or damage your car, your camera or your gimbal or any other items in the crash it is at your own risk - we recommend you self-insure for 3rd party liability and loss (you hit somebody or yourself) - talk to your current home insurance company before you fly.  Manage your Risk.  NEVER install a camera unless you are prepared to loose it in a crash. Noobs must use GoPro inside the crash-resistant case !  Never fly closer than 30m from persons and never fly over crowds or public gatherings.
  • Excludes support for items we don't sell - if a cloner-shop or forum-shill sold you something - we don't support that product, and will NOT discuss that product or how it may or may not integrate with the PARIS Sirius™ v5 Mega iOSD - go to the PARIS forum -> the Forum is the best place to chat about on-topic DIY setups
Mounting & Care
Mount PARIS with the IMU on top side and the IMU arrow facing forward.  The compass arrow must face backwards. The GPS must face up, be located away from impact risk,the tan colour ceramic antenna "up" and must be in an open area to receive sats -  NOTE : GPS lead wires MUST be routed well clear of EMI - minimum 75mm from any ESC or Video Tx or uBEC - We recommend route wires on the other side of Carbon ; or wrap wires with adhesive copper tape here in zones where they pass close to such devices - GPS wire route/shielding is CRITICAL to good GPS signals    
 IMU - Do not store the IMU on its side or upside down as the PUGel can slowly detach under gravity - PU gel can be washed in clean water and will regain 100% adhesiveness - always check the IMU is stuck down flat in your pre-flight checklist - PARIS v5 uses the standard 45mm Square mounts found on ALL Scarabs - Use Nylon screws/standoffs to mount PARIS.  Metal screws and posts can short the PARIS.  Never run the PARIS bolted hard/flat down on a Carbon plate as carbon conducts electricity ! - short circuit will permanently damage the PARIS - We recommend that you mount the PARIS under the protective dome HERE - This product is a sensitive electronic component (naked) and can be damaged by salt air, moisture, Static electricity from clothing, short circuit, over voltage or by live connection of ESC's - Use with CARE. Do NOT take-off and land in clouds of dust - these dust particles can come to rest on the PARIS and form conductive bridges resulting in permanent damage - for dusty or sandy beach sites always use a Helipad mat such as a large boot-mat from your car  -  As a rule POWER OFF before connecting to other components (always). POWER  is 5v via BEC "red wires".  The PARIS must be protected from Static - clothing or low grade soldering irons.  
Set up and build for Clean Data    I2C data bus wires should be 1) as short as possible 2) twisted 3)not pass over each other or near serial wires 4)if using a long IMU wire then compensate by moving the MAG wire to a short wire.  check the GUI for i2C errors caused by interferences.  Be sure not to connect oLED to front HV port and apply set up criteria above
  1. Protective coating - It is critical to the I2C data that no device creates spikes - data spike on one sensor effect all data on the combined bus, so a bad oLED will induce I2C errors, it will effect IMU ability to transfer data and may cause a crash  - so if you damage your compass wires it must be removed and replaced.  If you connect a oLED to the wrong port (should be front HV not rear) this can produce hazardous data spikes leading to random twitching.  We highly recommend that you use Lanox or similar non-conductive anti-corrosive lubricant sprays to get the best from the PARIS - Any pin connection with push-on connections will be massively improved by a very light coat of Lanox. Avoid spraying it wildly - the best way is to spray a small amount into a tub - then use a screw driver tip to transfer the tiniest amount to pins - including critical C-PPM and I2C data pins, ESC pins etc.
  2. Wires - Never ever pull on wires to remove a connector ! really bad idea. -  to remove a push-on-connector you must grip the connector itself and gently rock it side to side while pulling.
  3. 10-pin connector - to install the 10 pin connector do NOT push with man-force as the 10 pins each require to be spread slightly to accept the male pins - you may end up push the connector off th PCB outside the terms of correct use /warranty -so, first locate the connector the correct way around and push it lightly in place - then use long nose 45° pliers to pincer/squeeze both side of the connector together with a drop of lanolin above.
Important Note - Recommended Supply voltage is 5.0v -> 5.1v maximum from Carbonbird ESC BEC's - this power can also be supplied by USB-5v (for setup) - but for an assembled copter 5v power comes from the ESC's 5v BEC voltage regs via the main Lipo, via the red centre Vcc wires of the ESCs.  NEVER attach 12v power or 16v power to any part of the PARIS board. The only exception is FPV centre pins - in/out centre pins marked Video in/out - these are connected to each other only as a pass-thru  - nothing else above 5.1v can be connect to a PARIS.  Rssi voltages must not exceed 1.1v.  In a Quad all four ESC supply power in parallel. If any one ESC becomes hot with motors stopped - simply isolate that red Vcc line - power down - disconnect the ESC white/red/black lead from PARIS v5 _> PARIS v5r3 irecommended to be powered ONLY by this 5.0v Switching uBEC HERE
How to power up PARIS v5 when connecting to a PC or Mac
If the PARIs is NOT installed in a copter it only requires 5v from the USB lead itself - however, If the copter is built and the Paris v5 is already installed - then remove the props • (install the FTDi driver) - see below - First connect the USB - then connect the LiPo to the ESC's (ESCs contain 5v regulators on the red centre wires)  • beeping will stop - then start the GUI. see below.  USB alone cannot power the PARIS and also the ESCs - so the beeping motors tells you to connect the LiPo - Props off!
There are 4 LEDs top-side , 3 LEDs bottom side and 2 LEDs on the GPS Red (for Satellite position lock) /Blue(GPS Power) on the lower side,; when first connected the GPS will blink blue only at 2per/sec, after GPS is locked and a position serial stream is being sent down the wires you will see rapid blue 4per/sec and red 1/sec - on the bottom side the RS232/USB comms leds are both red for Tx/Rx - the OSD 328CPU has a green LED.
  1. During Arduino Code loading the blue LED will flash
  2. After clearing eeprom - the blue top led will be solid blue - dull
  3. After reloading PARIS v5Mega iOSD specific code from our base code - the leds will show steady green and pulsing red/blue - Once calibration of the ACC is done the red/blue pulses will stop - provided the PARIS IMU is level
  4. During first ACC-CALIB the red/blue will be solid and the green will pulse.
  5. After successful calibration of Acc (very first time to eeprom) green led will pulse slowly - alone - be sure to see a slow green pulse before arming
  6. if the ACC detects a tilt of > more than 20° it will flash red/blue
  7. if the modes are set for GPS/BARO before arming - then the PARIS v5 2.3 firmware will not ARM for safety
  8. During MAG calibration the Red/Blue LEDs will pulse FAST for 30secs to indicate to rotate MAG slowly in XYZ 360°
  9. The yellow LED top side main board is planned for future software release update to show Hero mode (full manual acro)
  10. in Horizon mode the green led will pulse 3per/sec
  11. in ACRO HERO Mode the same green LED will go solid green
  12. in ANGLE mode the same green LED will go OFF
  13. You should not attempt to ARM with BARO ON ; nor NAV modes on (GPS PH or RTH) ; nor tilted - ie there must be no RED flashing LED on the top side of the PARIS v5 before arming - use the oLED and LEDRing for further LED info
Attached hardware
This MultiWiicopter.com website contains itemised-wiki product information for each part attached to a PARIS autopliots - so if you have a question about an "ESC getting hot" that is attached to the PARIS MEGA - go to that ESC page and search for the word "hot" relating to that ESC product - if you have a Question about your attached motor - go to that motor page  -so go to the relevant parts page drill down on this website. There you will find info on that drill-down item topic's page.  If you want to know how to use the oLED go to oLED page on this site etc.....
Software is OPEN Source
Multiwiicopter software called MultiWii is open source - We manufacture the hardware -  the hardware is Plug-n-play - this means no soldering - It DOES NOT MEAN PLUG & FLY- You first need to understand the software mode functions (above) fully - use the GUI below to calibrate your Transmitter (takes 2 minutes) and check switches set it up, just so you know which switch does what function?  (unless you purchased the Transmitter from us, in which case calibration already done for you - just confirm it in the GUIThis product flies on software -  open source code - Its extremely good - The manual mode is by the best of any -  however, we assume no responsibility for the code base or its function meeting your expectation or understanding - it receives acclaim daily in live forums and on Facebook - Use with your own SMS plan based on your skills, observations.  Be sure to do range checks, and check the function and setting of FAILSAFE which is pre-programmed by YOU the user into your RC Rx.  

Replacing or updating to a new Master Sketch firmware file
- If you wish to change the type (i.e. Trii to quad) and you are confident 100% the sketch file you are about to load is correct (this is serious) - then the way to change the firmware is as follows (for experts only - at your own risk and duty of care) - essentially you upload a new firmware sketch file.  Making sections active requires commenting them "in" by removing the // infront of that code line.
  1. if you want to change the code - use Arduino 1.8.2 to open the sketch, 24th tab called config.h, (best not assume anything - you must be sure the sketch commenting/code is correct for the attached hardware) - Go to config.h tab and double check all code meets your setup.
  2. or ; if you have already got the sketch file on hand ; select Mega 2560  select-mega.jpg
  3. select the correct USB port for the PARISv5 such as COMM3 (will be different for any PC or MAC) serial-port-for-paris-v5.jpg
  4. first upload the file "clear eeprom" - twice - then
  5. then upload this new 100% correct sketch (keep a record of it somewhere as the sketch CANNOT be read back out!)
  6. launch the GUI and redo the CALIB_ACC with the Paris IMU 0.00° level
  7. the GUI runs under JAVA 6 - so for Apple Mac OSX Yosemite you will need to install the older Java 6 here in order to get the GUI to run, and also to run Arduino 1.0.6 too for that matter - Java 6 works fine after this is done - We use Yosemite OSX with java 6 ourselves
v5r3 AutoPilot Software GUI & RC setup - Props must be OFF - The following steps MUST be completed
  1. Make sure your PARIS board is insulated - not touching metal or Carbon - to prevent shorting pins on the lower side - ideally sitting on a wooden desk or an insulated surface if at your PC 
  2. Download PC 32bit (even if you run a 64bit) or Mac OSX FTDI USB drivers here - install on your PC or Mac - then shut down fully - wait 1 min - restart to activate the USB driver
  3. Download Arduino 1.0.6 Here - this is important for PC users, install it, even if you don't use it, as it contains the driver libraries - different versions - each works with Mac, MacBook or PC win 7/8 (sure we know Arduino 1.8.1 is out now but may give "compile errors" on some PCs - Download and & install the older Arduino 1.0.6  HERE PC_Win7 or HERE Mac 1.0.6 OSX )
  4. optional - If you want to browse or alter our custom specific 2.3 sketches for the PARIS v5 MEGA iOSD (3rd Nov 2014) - download them HERE - (but they are not essential because they are already loaded and tested - do not try to use these with any other PARIS board - only the v5 and only for experts - uploading code can wipe saved setting and wipe factory calibration - please realise the software 100% controls the autopilot - reloading it is a major responsibility and not suited to noobs)
  5. Install JAVA from HERE - then restart your PC/Mac - connect the PARIs Micro USB to your PC USB . The 32 bit GUI (Use the 32bit version even on 64bit PC) requires Java is installed and running - recently Mac OSX has removed java - we use and run it under Windows 7 and also Mac OSX Yosemite with no problems - be aware that JAVA security is your risk on your PC, be sure to run a full Virus blocking agent on windows such as http://www.f-prot.com/ -  For Apple Mac OSX Yosemite you will need to install the older Java 6 here in order to get the GUI to run, and also to run Arduino 1.0.6 too for that matter - Java 6 works fine after this is done - We use Yosemite OSX with java 6 ourselves - For PC users experiencing JAVA setup problems, you can choose to use the alternate WinGUI here (WinGUI does not require JAVA.) however we dont like  WinGUI as its a tab-fest and fails to use modern HD monitor space effectively, leaving you clicking endlessly through tabs.  You can also use a BLE Bluetooth and do all your settings on an iPhone , works great - the only thing you cannot do by bluetooth is load new code like a new sketch - but it works very well for all other types of setup and monitoring.
  6. Connect your RC Receiver to the PARIS - see photo above for FrSky Sequence/Futaba Sequence/JR Spektrum sequence- see taranis page for Rx side colour sequence.
  7. Turn on your Radio Tx transmitter first (always turn on a RC Tx first - and turn Tx off last - otherwise your Rx will go into failsafe mode - if failsafe is setup? - make sure to do that before a maiden, if not already done!)
  8. Bind your RC Rx to the RC Tx - see radio manual - for Taranis see 2nd paragraph HERE BINDING - when done your Rx will have a steady green LED
  9. Download the matching v2.3 GUI java app HERE - (Do NOT use v2.2 or v2.1)  first UnZip the downloaded files - then, Open the file called MultiWiiConf.exe (inside the windows32 folder for PC ; or MultiWiiConf23.app (Mac OSX)  
  10. The JAVA interface requires clicking with a mouse - fast jabbing micro clicks are too fast for the RS232 interface to register and we advise a steady 0.5sec click in the top left side of any box or button, to get a result.  DO NOT PRESS RESET ! it will wipe all our settings :( - take a moment and read carefully below.
  11. Select the comms port (PC it is called COMMS 3 or similar) (for Mac - its a AlphaNumeric 9 digit - as below dev/TTY.USBSERIAL-A7030WKI or similar port)
  12. Select the board type as MEGA 2560 (if using Arduino 1.0.6)
  13.  Wait 8 secs ; then press START  (failure to wait , or clicking multiple times before PARIS can complete the startup cycle can wipe all PIDS to ZERO! - be sure to wait )
  14. Wait another 3secs and press READ
  15. paris-v5-mega-osd.jpg
  16. Calibration in the GUI  - The PARIS v5 arrives with GYRO and Acc already calibrated - sitting on your desk the ACC numbers should be approx 0/0/250 - if the board is tilt a little they will be  similar to this 16/-19/252 - be careful not to un-do whats already done by clicking calibrate wildly or randomly ! - The IMU arrow faces forwards - The Gyro and the Acc can be re-calibrated (in the future if needed)  in the GUI by holding the IMU at 0.00° level -  motionless for 5 secs - click-pressing CALIB_ACC  - not moving - after about 6 secs you will see the Acc data will reset and show 0/0/250 approx 
  17. The MAG arrow must face backwards on your Quad - the mag should be positioned away from all other interference sources - DO NOT place the MAG in the centre of the Quad near ESC, Battery or wires - ideally it will be at the end of the tail or on a FPV mount bracket - then and only then - Press CALIB_MAG - in the next 60 secs the entire Quad needs to be rotated one turn on X,Y & Z axis within 60secs of pressing CALIB_MAG
  18. Getting your RC Radio sorted - removing stick errors you never knew your RC Tx had - so now look at the top right Blue-on light Blue-bars - each one will move in conjunction with your RC Tx Rx moving when connected and all RC powered up - when sticks are centred the reading in the GUI (via USB) should be 1500 .   When the throttle is placed at idle/off - the THROT GUI bar should bead <1100 usually 1090 approx - at full the throttle should read 1905 approx - also check the other three sticks are 1095/1500/1905 approx - if you purchased your radio from us this is already done for you.  If these are not correct they are adjusted by making changes in the Radio core menu whilst "looking" at the PC GUI bars - these RC setup menus are called by various names depending on RC brand - TRAV/End Points/SubTrim/Centrepoint etc see your radio booklet - (NOTE: don't ever make changes on the trimmers on the front of the Radio as these might be bumped later sending false roll commands to the v5r3).
  19. There are 3 windows in the GUI - MultiWii.com/Servo/Settings - Tricopter note - Tricopter Minus-one is the default setting - to reverse it (only if needed)- in the 2.3 GUI - click READ - then SERV0 ; then GO LIVE ; at the top click the white box to reverse it - then click WRITE.  Be sure to click boxes with the mouse pointer at the top left of the box.
  20. The GUI cannot read USB connected after start - Quit the GUI and restart to see USB devices - If you see any unusual settings after calibrations - always restart the GUI and re-power the PARIS (remove USB) before you start creating problems - so you see something strange - STOP - power cycle the PARIS and re-start the GUI - FIRST - then investigate further.
  21. setting-multiwii-servo-gimbal-setting.jpg 
    For GIMBAL camera tilt see Tech FAQ Here ; to be read in conjunction with viewing the video showing how a camera can be tilted down by Aux3,Aux 4 or even aux 5 (for SBus) is here
  22. setting-multiwii-mag-declination.jpg
Note 1 : Changes to the GUI switches - a white square means "active" - grey means inactive - click the upper left side of any square to activate it - then to save that change, press WRITE.  To change the value of a number - Click->drag it with your mouse. Then press WRITE.
Note 2 : Advanced users - if you are doing Arduino code commenting - Always clear EEPROM twice, if/before loading new PARIS v5 specific sketch code.  Beginners - NEVER reload code - chances are the code is wrong and you will create problems you cannot solve.  
Scarab OSD R1.3 (below info) includes Pre-Proggrammed iOSD v1.3 (new vrsion 1.3 is effective from 17 Feb 2015)
How to use the iOSD GUI  ?   - Answer = it's easy to access this iOSD setup screen in your ground station, if you want to make changes -  
You can either : -
a) use your Futaba/Taranis Transmitter to make changes live via your Tx sticks and viewing your Ground Station screen
 (the usual way to do it)
 Whilst dis-armed ( the first time take your Props off incase you mis-manage the process - if motors start, you messed up)
  1. Set your throttle to mid point ; first - keeping it at 50% throttle -then
  2. yaw right & pitch the cyclic full forward
  3. You will now enter the live set-up mode (you will be at screen 1, PID’s)
  4.     • You can exit at any time, without saving any changes, by putting throttle to minimum
        • To move between pages, yaw left or right
        • To ‘tab’ up or down between fields on a page, pitch forward or back
        • When on a field, yaw left or right to change values
        • To save changes, pitch back until the cursor is on the bottom line, pitch left to ‘save and exit’, then yaw right to action the ‘save’
  5. BE SURE NOT TO EXIT BY MISTAKE AND ARM THE COPTER - take your props OFF the first time - to be sure you understand this can only be done safely - > WHEN DIS-ARMED.
; or b) make changes on your PC/Mac with the hacker card (not recommended because you have to disconnect all ESC, disconnect your Bluetooth, disconnect the serial (3) plug and connect a hacker USB) - we recommend the RC Tx method above
The PC /Mac method follows below - paris-iosd-usb-uart-2581b.jpg
In your PARIS v5r3 the pre-loaded R1.3 Scarab OSD software is Open-source and we have specifically edited the values to suit our hybrid 5v minum+ hardware - here is a separate GUI for alterations to iOSD - to fly you do NOT need to initially make any changes within this iOSD-GUI or even run it - not even once - unless you want to change PAL->NTSC for example, as the OSD is pre-loaded into the PARIs v5 Mega iOSD ; The iOSD GUI is different GUI to the PARIS autopilot GUI - we have preset the "switch" for 2 levels of OSD data; a "full data" option and also a minimum data option by selecting a switch for AUX4 - If your at expert level you can choose to alter it, but we strongly recommend NOT to, rather go fly first - then make changes later - All changes are at your own risk ; changes are done with an optional FTDi devices HERE.  wires - Be very careful to gently rock the 4 pin Serial molex for SERIAL3  and pull it out gently by the rocking motion. Damage to pins and wires can be caused by incorrect technique or undue forces.  If using an older red FTDI then Connect the supplied cable as per this colour sequence in the photo above, to the male molex and run the R1.1 OSD GUI - download it from HERE - install 32bit version even if your PC is 64 bit.  To run the iOSD gui we recommend to disconnect all the motor ESC control wires, camera and Video Tx from PARISv5 first.
Launch the KVTeam OSD GUI - for details please watch the video below. - light blue switches are "on" in the left position - "off" to the right side position.
You can change the PAL-NTSC or NTSC->PAL via the iOSD GUI itself - flick the switch over then press "WRITE"
For people who have the older red style FTDi -> use the supplied cable - SEE photos above for correct pins setup
For people who don't have an FTDi (and don't want to save changes live on their ground station)  be sure to purchase the New "hacker" FTDi here - is very easy to use - instruction on that products page
Replacing or changing the iOSD code - Experts only - If you choose to alter or re-load the iosd Sketch first disconnect the ESC control wires from PARIS, disconnect Video in/out  (and BEC if fitted) only the Hacker will be connected when re-coding the OSD CPU - The OSD R1.3 Sketch file is HERE and is loaded with Arduino 1.0.6 
We recommend to use the hacker ftdi and hold down the interrupt whilst compiling - release precisely when it says "loading" (within 0.5secs - for this you need to disconnect the ESC's) - you will then see both red/green leds flickering on the "hacker".
If using a red ftdi - remove the GND pin and insert it back in when it says "loading"
Experts only - If you need to reload the font for whatever reason, it is here
  1. Question Why is my OSD only showing a plain black screen on Ch  - Answer- you have the camera and the Video Tx plug into each other's pins port - the Camera goes in the top pins with yellow towards the middle of the PARIS - The video Tx below that
  2. Question Why is my IOSD data displaying on/over a black background? - Answer - Most likely you are running a 5v Fatshark/immersion system mixed with a 12v CarbonBird camera.  The camera is not receiving 12v - The PARIS v5 iOSD pins pass thru the voltage Vcc on the centre red wire - for mixed voltage systems you need to power each Red Vcc separately. Be careful not to send 12v to a GoPro !!!
  3. Question I see a picture from the FPV camera - but nothing from the OSD data? - Answer - The default setting is for a 60 fps NTSC camera - if you have a 50 fps PAL camera you need to change it in the GUI to PAL.  The other possibility is dirty voltage - the Scarab OSD is designed to run on 5.0v from ESCs - we have tested it with all carbonbird ESC.  the MAX chip is NOT compatible with 5.4v switching uBECs.  The recommeded switching 5.0v quality uBEC is HERE
  4. Question My GUI shows I2C errors - answer - this usually indicates a software to hardware mis-match - one or more I2C devices like the IMU or the MAG configured to be active by code is not responding or is not connected at all, or is connected but not correctly or its wires/pins/plugs are damaged.  if you see wild readings/graph spikes and massive i2C errors - stop don't fly - power down then remove one I2C device at a time and re-power; see which device is damaged or which wire is receiving interference - make sure you don't have an HV i2C device in the rear-only 5v port - move it to the front 5-pin port.  I2C errors can also occur if you do not route wires clear of other wires - for example if you have the compass wires crossing or running together with the GPS wires.  Be sure if extending the IMU I2C to reduce the MAG wire lengths.  I2C rule is short wires clear of interference from other wires.  The GUI also shows numerical data for each sensor which is useful for troubleshooting setup issues (for example if the mag data is unusual it is most likely the MAG...)
  5. Question My ESC's beep non stop - answer - ESC have multiple safety system to prevent you from chopping yourself up when you first connect power - make sure you have the throttle stick all the way down/back and the THROT blue bar is less than 1100 - props off - then connect the LiPo to the ESC power distribution system - the beeping will stop - if it does not this means you have not yet calibrated your ESC learning curve to the 1100-1900 multiwii range - see ESC learning curve in the Noobs guide page 11/12
  6. Question My GPS does not show my position - the GPS cannot work inside - it requires a clear view of the entire sky, go outside into an open field.
  7. Question The compass behaves weirdly - To use the compass you must have it 100% physically synchronised to the IMU (both the IMU and the MAG attached to the quad - IMU arrow forwards - MAG arrow backwards)  - so both items - the MAG and the IMU must be attached to the airframe in their final permanent spots. MAG on the tail, IMU in the centre of the craft - then when you rotate the craft they will both work together - north is UP.  MAG calibration cannot be done near metal objects or electronic devices like PC's
  8. Question - My PARIS does not return directly to home when a select RTH? - the MAG cannot just be located anywhere - select a good spot for it - arrow facing backwards  a) where it is NOT disturbed by iron or EMI b) the MAG must be free from vibration c) the MAG must be calibrated outside far from metal objects - not done next to a metal desk, metal wall or car or cell phone.  Use the two dollar compass as a canary-in-the-mine to tell you if the MAG is getting interference. 
  9. Question - My PARIS does not arm? - Answer - Make sure BARO is OFF - Make sure navigation is off (RTH and GPS Hold) - Make sure you only see green leds on the top of the PARIS v5 - if you see RED/Blue flashing - then either the tilt-no-arm protection (aircraft tilted >20°) is stopping you from arming  ; or you just loaded some new sketch yourself and have not yet done the ACC calibration (this does not apply to new PARIS v5r3 as this is already doen for you prior to shipping)  - SEE bottome of this page to arm/disarm - Some of these reports "not arming" reports are traced back to customers still using their older v2.2 GUI or older! , leading to various problems especially as the calibration then become corrupted if you have pressed the Calibration button in 2.2GUI using this newer 2.3 firmware(You must now clear eeprom 3 times and reload 2.3 firmware and re-calibrate the Acc).  So please, Make sure you are using GUI2.3 ->  the correct matching version 2.3 GUI HERE
  10. Question - What is Reference Voltage 5v   Answer = If using 4 cells or 3 Cells, and no analogue sensors are connected as above, using (a default 1.1v) reference is the preferred choice as it will provide a more stable and accurate voltage reading - just leave 5v reference voltage OFF.  Conversely Use Reference 5v is mandatory for 6S Ops.  It is MANDATORY to select a 5v reference to "ON" if any of the following are true:

    Using more than 4 cells - i.e. 6s ops
    Using analogue RSSI connected to the OSD
    Using a hardware current sensor connected to the OSD
  11. Question - I am a noob - I am afraid that i will crash on my first flight ? I was thinking to have all modes activated?  Answer - No sorry bad idea because you don't yet understand the consequences of these modes (for example the mag will try immediately to rotate the craft back to face the way it was powered up).  Use the GUI above to make sure you know how to set your Ch switches for ALL MODES OFF - to have no green bars on any advanced modes (all will be deep red - none green - in the example above you can see that the switches are set to have ANGLE/MAG/BARO/HEADFREE "on" - not suitable for first maiden - turn them off and they will go red)  The correct way to approach your first flight is to do a hand maiden with a small quad first - test all controls responding normally - all motors responding normally at low power  to disturbance - any down-going motor is speeding up - no strong yaw forces trying to spin the craft - - then stand behind the aircraft and hover in HERO Mode (gyros on only) - its easy -  if you throttle up to 50% the quad will jump up and sit there - be ready to smoothly pull power off to land. As you become more advanced - turn on ONE mode at a time to learn it. 
  12. Question - How do I know which mode I am in? With props off, inside attached to USB and the main GUI running as well as all your RC Tx/Rx on - flick your Tx switches and then note the position for RED = OFF for each mode - mark your Tx switches with Label-tape. Practice turning modes On/Off while watching your PC GUI interface - once learned - disconnect from the PC and go outside to fly - One other way is to purchase a 5PIN oLED which will show you the modes in the field or if you are in OSD mode it will show all modes OFF acro - or stable - Mag - Baro and GPS being on - (Future software version are planned to illuminate the Yellow LED to show ACRO mode via software)
  13. Question - I have the newer v2r1 GPS/MAG - how can it be connected and coded - The new GPS can be run as a single wire I2C GPS/MAG and coded I2c GPS - or run as a separate 2 wires Serial GPs and I2C MAG for 2.4 navigation - set GPS comms speed to 57600 port 2 - Face the Scarab logo up and forwards.  The Red LED with pulse 3 time radid - pause - 3 rapid when >5 GPS are found and a FIX is obtained and sent to the PARIS CPU - home point.
  14. Question - Can PARIS v5 do waypoint navigation? Yes using MEGA PIRATES NG 3.0.1 - We have designed the PARIs v5 to also run Arducopter hybrid code called Mega Pirates NG which has a full mission planner - this activity is for experienced pilots and NOT for beginners.  Working with MEGA pirates is going well for PARIS v5. Aleksey (Sir_Alex) in Belarus released the newest new MPNG 3.0.1 R4 code with support of your PARIS v5 boards  The instructions, on how to compile and connect components is on MPNG site below. MegaPirates have a good wiki, all instructions are there. here some extracted links from his site:

  1. Question - Can PARIS v5 control a gimbal, i want to tilt my camera down inflight?  Yes it has both gimbal pitch (pin 44)  and gimbal roll (pin 45) Gimbal outputs running for all copter types and camera trigger servo output (on pin 46) for details on how to setup RC for Servo camera live TILT on Aux 4 or Aux4 see Tech FAQ here- however this is for SERVO based gimbals - The newer Brushless gimbals are self levelling and do not need to be connected to the PARIs v5 Mega gimbal drivers at all.
  2. Question - I heard that Multiwii is too complex and needs coding - Answer - Not true.  MultiWii uses a Mac or PC user interface called a GUI.  You can alter magnetic declination for your Country; servo limits of a servo gimbal ; PIDs ; and even reverse a Triikopta servo - all in the GUI  - The GUI is used to set PIDs and also calibrate/check the accuracy of your RC radio - in the same way dji requires you to follow a calibration process - the difference is that MultiWii requires you alter the radio to be accurate (sub trims and end points) rather than "fudge" the radio errors and interpret them to be accurate - after setting your RC radio up using the MultiWii GUI it will actually be running better than when it left the factory - removing all factory errors.  MultiWii code only requires "commenting" in or out - you NEVER have to write code.
  3. Question - I want to overlay OSD onto my GoPro 3 (5v camera) but my FPV tx is 12v - Answer - Be very careful - the GoPro is a 5v camera and the FPV Tx is 12v - so the centre red wires in the three wire video leads must never be connected to each other (inside PARIS v5 both Vcc lines are connected to each other in->Out !)  - make sure the GoPro wire HERE, only has a yellow & Black wire only - with no red centre wire - going out to the GoPro.  The GoPro will run with 5v coming from its internal battery or you can use an inline 5v reg sold separately HERE
  4. Question - I have used PARIS v4 with software 2.2 before -but  What are the changes in software v2.3 MultiWii in general?  The main change was the complete re-write of the yaw code - there were many many changes in the code - you can read about them here  - be sure to use the new GUI v2.3 !
  5. Question - Can i upgrade to my OSD to new/next versions? - Answer = Yes - this is covered in the open source SCARAB OSD site here 
Connecting ESCs/Motors
NOTE: Never connect or disconnect ESC or SERVO pins while PARIS is powered up & Live or while ESC are live !! - if you reverse connect or connect pin high you can permanently damage the PARIS CPU output transistors, resulting in no response from that PWM channel  - always connect all servos/ESC with power off - only connect 5.0v to the PARIS last after all other connections are double checked correct - this will ensure a long life - If you operating in a salty coastal area - spray all push-contacts with lanolin spray such as GoldX or Lanox - The Black and red wires can never be swapped around !!  be sure NOT to reverse the polarity.  Make sure any uBEC can provide 5.0v (NOT 5.4v) and sufficient amps for the Gimbal servos.  The recommended uBEC for PARIS v5r3  is HERE
Question - I have damaged one my output transistors doing a live wiring hot swap , one ESC/Motor now beeps - i think its a blown pin error :( ooops  -Is there any way to stop it beeping and get that motor/ESC working again and save my PARIS v5r3? Answer = good news is if your flying a Quad or a Vamp - There is a work around for you, yes - The output can be re-routed to another pin using software - see this post here http://www.rcgroups.com/forums/showpost.php?p=28804615&postcount=4352 for a detailed recovery - Thanks to coder PeterWebb for his contribution.


  • Select soft "flexible" props with a low pitch such as 10x5 and wide span to give a large amount of slow moving downwash.  In the hover the throttle should be 1/3 to 1/2 maximum.  Carbon props look cool but there are serious issue with rigid stiff props and associated vibration they can cause in fast flight !
  • Use a prop-balancer to balance all props statically in 2 dimensions - absolute balance is essential for AP Ops ; then run them individually to check they are centred true and the tips have the same path ; any vibration will reduce the effectiveness of the gyro and the Acc
  • Keep your PROPS OFF - not installed - until you are fully conversant/understand in full the functions of your Tx in full including TRAV (end Points), the arm and disarm procedures -  realise that for a noob skipping or out-of-order set-up steps or moving sticks, or even static -  PROPS may start at anytime without warning.  Never install props prior to calibration of the ESC and testing the gyro orientation, and arm/disarm testing of the board - YOU are responsible - make sure your actions and your Copter is safe.  
  • Always hand maiden first - any down-going motor must speed up - then first maiden on default PIDs' - If the copter is not almost perfect on default PID's then DO NOT go straight to massive altering the PID's!  MultiwiiCopters require good quality ESCs such as or CarbonBird® (Not SimonK ! ) then do full calibrations of all the ESCs, the correct timing set/programmed into the ESCs and lastly good quality wiring and soldering (not 3.5mm press fit connectors) - Use FLUX PASTE to complete all soldered wires. 




Using the Tx sticks to operate the PARIS 

Set the Throttle to OFF/LOW (and check the GUI 2.3 to be sure your RC radio is not reversed either) - After connecting the LiPo - The ESCs will beep to indicate they are powered but not armed  -ESC's cannot arm on power-up with PARIS AIR.  The embedded software prevents this and requires you arm with a stick combination below   The red LED comes on (steady) on the CPU board showing the board has power.  After connecting the LiPo (or USB) the green CPU LED will flash for 5 secs then go OUT   If the LED blinks green (fast) but won't stop blinking - then the Rx is not powered by 5v (an Rx cannot get sufficient PWR from some USB! It must be powered by 5v from at least one BEC).If the green LED still blinks green (fast) but won't stop blinking -then the Rx is not connected to the correct PARIS/warthox THRO pin correctly.  The ESCs cannot calibrate as a multi-engine-group because the default state of the CPU->ESC is Dis-armed for all engines.  You need to calibrate ESC throttle-learning range as a separate exercise -below
If the ESC's beep-non-stop then they are not connected to the PARIS board ESC pins or the Rx is incorrectly connected or the Rx/PARIS sees you do not have your throttle to zero.
If your copter goes out of radio-range it may cause harm - if still powered - Take the precaution to program in the FAILSAFE condition to protect people/property.  Do not skip this step.
Bind your failsafe (Read your Radio manual - FAILSAFE) on the Tx with power/Throttle DESCEND failsafe condition.  You might decide to set the failsafe power to 40% throttle so the aircraft descends in a controlled descent - recommended if understood - For Example on FrSky - set sticks as above (or THRO to 40%) - then Press the Rx button - 2 green flashes on the Rx itself - done.    Failsafe can also be set in MultiWii Software (this option is NOT recommended - Use only for ultra basic or legacy Tx's like turnigy 9x  - if your Tx has failsafe Like all JR/Futaba/FrSky- use hardware failsafe in the Rx). When you turn your Tx OFF in a test the Failsafe   -  should return the Copter to level and min-throttle - 
NOTE : If you use a 33%-40% power (controlled descent setting) be aware that if you switch your radio off while the PARIS armed - then you will initiate a 1/3 powered condition!  This is why the Radio must go "on" first , and "off" last.
You must understand this concept fully and realise the word failsafe - does not mean you can be an idiot yahoo - sorry - you still need to understand the consequences of your chosen "failsafe" condition - and You will be deciding what YOUR Radio "pre-set" will do when it cannot receive a signal.  You are still the Pilot in command - YOU are responsible to decide how you will handle failsafe above.
Arming - Learn to recognise that your multiWiiCopter is ARMED.   In MultiWii 2.3 or later there are several safety no-arm "blockers" (for safety)- you cannot ARM if tilted ; you cannot arm if BARO is on ; you cannot arm if GPS is on.  to ARM -> keep throttle below 1100 uSEC (off) then Hold right Yaw (or right cyclic) for 1 sec - you will see the LED come on - stays on SOLID
If the andromeda LEDs does not come on and stay on solid - then increase YAW travel on the Tx to 110% (see Transmitter Calibration procedure - above top) - or Check the THRO is not actually reversed by mistake (Futaba) - USE THE PC GUI it will reveal your actual numbers - if your stuck out in the field with no PC - then trim down a few clicks on the THRO trim.  If it still won't arm connect FTDI and use the JAVA-Config (see below - install JAVA) to make sure the Throttle PWM is below 1100 (normal THRO range is 1095-1905) - In order to arm - the Wii  CPU is looking for THRO and is a valuable guide to trouble-shoot a CPU which won't apparently arm.
Disarming - Learn to DISARM the ESC's before touching or approaching the Copter ESC's/Motors can start suddenly and the props can cut fingers and eyes - permanent injuries!! so With THRO OFF ; Hold the YAW stick LEFt for 1 sec ; then the CPU GREEN LED will go OUT and stay out
Gyro Calibration - Disarm the copter (see above) ; Place the Copter on a perfectly LEVEL LZ - it must be completely static - Check all Tx Trims =  neutral - Stand back - With THRO off, Hold the YAW LEFT and the Cyclic stick Back for 1 Sec ;  release - you will see the GREEN LED blinking fast for a few secs then go out - The Gyro is now calibrated for gyro drift (at this ambient temperature) - Note : The Gyro on a PARIS board now auto-calibrates in first 4 secs after Powering up - in the outside air temps where you fly.  However the Acc does not - see below.  It still pays to know how to do a gyro Cal - and if you get any strange drifting behaviour - always do a Gyro Cal and an ACC Cal(below) - you do NOT need to re-calibrate more than once a month.
Accelerometer (Acc) Calibration - - you do NOT need to re-calibrate more than once a month. The PARIS is calibrated before shipping out, at 25°C - However  if you Ops are at a different temp a temp bias can be introduced need a re-cal, so for your Ops temp set the Copter level 0.00° - Press CALIB_ACC - (after first Flying the Copter in ACRO mode - Trim out any YAW using motor tilt (3-5°) - Dont use Tx trim - all Tx trims must be 0) - - Land - Switch over the HORIZON or ANGLE mode - hover STILL air (no wind)  - if the copter is drifting by more the 2° tilt the calibration is effected by temp and you need to do a field Acc Cal -> land - -  
Disarm the copter (see above) ; ensure the Copter is on a perfectly LEVEL LZ - it must be completely static - 
 Confirm the DISARMED LED is OFF - Hold Full THRO/YAW LEFT and the Cyclic stick Back for 1 Sec ;  
 release - you will see the GREEN LED blinking fast for a few secs then go out - The Acc is now calibrated for LEVEL mode (at this ambient temperature) - The ACC on a PARIS/warthox board is the Nunchuk®.  
MAG (Compass) Calibration - to do a periodic MAG calibration (or new Maiden of a PARIS v5r3) Move the aircraft to an outside area 15m away from cars, cell phones or any ferrous (magnetic) material (including PC's , buildings or re-inforced concrete etc) 
Make sure you are Dis-armed - all Modes OFF - ACRO mode -  cyclic (Elev) full back toward you. then move the throttle carefully to full/right yaw full ; to work it must be in that order... and (throttle >1900; Rudder >1900; Elev <1100)
PARIS v5r3 red/Blue LED will flicker very fast for 30 secs
During this time rotate the PARIS 360° - in X , Y and Z axis - finish with the craft level on its skids (or held level in your hands) 
the process is complete when the red/blue flicker stops and you see only green LEDs on top
Accelerometer (Acc) 2° Trimming - Also called auto-LEVEL trimming - FIRST do after the GYRO & ACC calibrations and normal ACRO trimming (see above).  LAND.   
Switch over to LEVEL mode (Gear Switch).   
Take off and mentally note the way the copter wants to drift - DO NOT TRIM THE TX 
- Land - The final ACC trimming procedure (below) is this -DISARM (see above - the Green LED will go OFF) Move the THRO to the 'Learn Position - full up) - in this example the copter was moving back and right - so ; using stick-banging - move the cyclic (right stick) up once (led blinks) - then left once (led blinks) - these alterations are saved to the CPU memory.  ARM again - hover and repeat the process until the copter hovers 'level'.  Each Stick-bang = 0.1°


 NOTE : GPS lead wires MUST be routed well clear of EMI - minimum 75mm from any ESC or Video Tx or uBEC - We recommend route wires on the other side of Carbon ; or wrap wires with adhesive copper tape here in zones where they pass close to such devices - this is CRITICAL to good GPS signals 

Write your own product review

Product Reviews

This product hasn't received any reviews yet. Be the first to review this product!

Currency conversion