MinimOSD Micro Setup Tutorial – Naze32 PID Tuning via OSD Menu, Display RSSI Voltage

by Oscar

In this tutorial we will have a overview on both normal size and Micro MinimOSD, how to configure and use MW-OSD firmware, connect it to Naze32 and RX, and firmware flash.

Some of the links on this page are affiliate links. I receive a commission (at no extra cost to you) if you make a purchase after clicking on one of these affiliate links. This helps support the free content for the community on this website. Please read our Affiliate Link Policy for more information.

What Are MinimOSD and Micro MinimOSD

MinimOSD is probably one of the most powerful, affordable OSD device for quadcopter and other multicopters.

The micro MinimOSD is much smaller but has exactly the same capability as the full size version. The MinimOSD we are referring to here is the one with KV Team Mod, which has soldering pads for RSSI, Current sensor, Voltage Battery monitor pins, so no extra soldering to the main chip required.

Buy the Micro MinimOSD from Banggood | Amazon

Although It’s more complicated to setup than those standalone plug-n-play OSD, such as the Super Simple OSD or E-OSD, it can do lots of cool stuff, and the on screen display is extremely customizable.

Some of the great features includes GPS data display, customizable style and fonts, using the OSD menu to change your PID and rate settings by linking it to the flight controller etc. Here is an example of full flight data OSD.


Adjusting PID in OSD menu. :)


Dimension, Weight, Pin-out and My Space-Saving Soldering

Full Size MinimOSD

This OSD has been around for years. The good thing about this MinimOSD with KV Mod is there are pin-outs on the side for RSSI, current sensor, voltage sensor etc. In the old days, people had to hack it by carefully soldering directly to the micro processor chip, which was extremely difficult and painful. With this modified version MinimOSD, things get much easier. The one I bought is the latest version V2.


Dimension of MinimOSD with KV Mod V2: Width: 21mm, length: 43mm, weight: 5.5g (with pin headers soldered)

minimosd-kv-mod-dimension-measurement-width minimosd-kv-mod-dimension-measurement-length minimosd-kv-mod-v2-weight

Micro MinimOSD

I am amazed by the micro form factor of this tiny OSD, yet it still obtains the capability of its full size predecessor. Except it doesn’t have the 12V to 5V voltage regulator, which isn’t used very often anyway due to historical overheat issues. So it was sensible to get rid of it and shrink the size down.

Check out this page for how much current it draws.


The micro version is roughly 1/3 the size and weight of the normal MinimOSD (with connectors).

micro-minimosd-dimension-size-measurement micro-minimosd-weight micro-minimosd-size-comparison-motor-2206

Soldering Connectors

Soldering of the normal size MinimOSD is easy and straight forward. But as for the Micro MinimOSD, I didn’t like the way how people normally solder it.


So I had a creative moment, and use 90 degree servo pin headers instead of straight, so I can save even more space when this little OSD is plugged in, inside the multicopter.

micro-minimosd-before-solder-conneector-pins micro-minimosd-soldering-pins-easy-access-compact micro-minimosd-soldering-pins-easy-access-compact-heatshrink-tube

And finally wrapped it with heatshrink sleeve to protect soldering joints and wires.

micro-minimosd-soldering-pins-easy-access-compact-heatshrink-tube-wrap micro-minimosd-soldering-pins-easy-access-compact-pinout

Connection with Naze32, Battery, RX, Camera, VTX

Setting it up in my quadcopter was actually very straight forward. Here is how everything should be connected: Naze32 Flight Controller, LiPo Battery, Radio Receiver, FPV Camera, and Video Transmitter.

minimosd-kv-mod-connection-naze32-d4r-ii-rx-fpv-camera-vtx-setup [normal size MinimOSD – connection with Naze32, camera, VTX, RX, Battery]

And this is how to connect the micro osd system.

micro-minimosd-kv-mod-connection-naze32-d4r-ii-rx-fpv-camera-vtx-setup [Micro MinimOSD – connection with Naze32, camera, VTX, RX, Battery]

FAQ 1 – Some people reported issues with OSD text disappearing when throttle up. Solution: connect all VTX/OSD/Camera to a common ground.

FAQ 2 – No OSD, only picture, or no Picture only OSD. Solution: Try to toggle PAL / NTSC in your OSD settings in GUI.

VBAT1 pin on OSD is connected to the main LiPo battery, to read the voltage level. RSSI pin is connected to the RX to get signal strength. (In this case, RX is the Frsky D4R-II, in CPPM mode, Pin 1 is PPM signal, Pin 2 is RSSI outputs)

By connecting the MinimOSD to the Naze32 through serial port (TX and RX), Naze32 can send flight data to the OSD, such as GPS data, quadcopter heading (compass data), changing PID with radio transmitter, and OSD menu and much more.

But be aware that the computer connection uses the same serial port, that means if you want to use Baseflight, or Cleanflight configurator, you will have to disconnect the TX and RX from the OSD first.

Without serial port connected, you can still run the MinimOSD as a standalone OSD, to just display RSSI and voltage data.

If you are using the Taranis in PPM mode, Check out this post on how to get RSSI info via a spare channel (without any extra wiring)

minimosd-connection-wires-mini-quad-setup micro-minimosd-connection-wires-mini-quad-setup How it looks like when connected inside my mini quad.

Config via MW-OSD GUI Software

There are quite a few OSD firmware available for the MinimOSD, my favourite one is the Multiwii-OSD (mwosd). The current version is 1.3, and the configuration software interface is very user-friendly. On screen display text is clean, firmware is more updated as it specifically supports Cleanflight and Baseflight. It also allows you to tune PID with OSD menu.

Connection between MinimOSD and FTDI Programmer

Either to configure it or flash firmware on it, a FTDI programmer is required. There are 5 pin connections required, DTR (GRN), TX, RX, 5V and GND.


minimosd-connected ftdi-programmer micro-minimosd-kv-flashing firmware mw-osd

Configuring MinimOSD with MW-OSD GUI

On the GUI, enable whatever flight data you need. Since I fly mini quad, all I need is battery voltage reading, RSSI, and timer. I use 4S lipo batteries, and voltage alarm is set at 13.6V (3.4V per cell, I should really set it higher). For 3S Setup, set voltage alarm at 11V should be okay. And my FPV system is in PAL format.


One thing that you need to play around to get right, is the battery voltage value. It’s way off with the default setting, and you need to play around with “voltage adjust” value until you get the correct reading. Here is how I did it.

Default “voltage adjust” was 200, and the voltage was 21.0V on the OSD. I used a multimeter to check the actual LiPo battery voltage which was 11.1V (you can also use a voltage alarm with display).

Now lower “voltage adjust” to 110, and the voltage was 11.5V on the OSD. To avoid going forth and back, we can now safely calculate the exact “voltage adjust” we need using algebra, and the information we now have. :D We just need to know how much OSD voltage reading every 1 “voltage adjust” changes.

(21.0-11.5)/(200-110) = 9.5/90 = 0.1056

We know the correct voltage OSD should display is 11.1V, so the “voltage adjust” should be:

110 - (11.5-11.1)/0.1056 = 106.21 (106 would do)

Update (01 May 2015): just realized “voltage adjust” can now be changed in the OSD menu, so you don’t need to connect the MinimOSD to the computer and open GUI to change it anymore. But if you are not using the OSD menu, you still need to use the above method.

Arduino as FTDI programmer for MinimOSD?

I tried to use my Arduino UNO board as a FTDI programmer as it worked before with some other devices. I managed to get it write/read settings to the OSD on the MW-OSD GUI software. However I was having trouble flashing firmware on it using the Arduino, I kept getting this error:

avrdude: stk500_getsync(): not in sync: resp=0x00.

It looks like a data sync issue, but I made sure I connected DTR to the RESET pin on the Arduino, not sure what more I can do, so I used my dedicated FTDI programmer in the end for firmware uploading, which works perfectly.

OSD Menu: Adjust PID and Rate settings, Voltage, RSSI

OSD Menu is my favourite feature of all, and that’s mainly why I switched over from Super Simple OSD. There are so many parameters you can change without connecting to a computer. For example I can now change PID values in the field using my radio transmitter, no Bluetooth or computer required! However it still cannot change roll rate and pitch rate separately for Cleanflight, at the moment they are still linked. (in the latest Cleanflight firmware, the two rate values became independent)

To access the in-built OSD menu in MW-OSD, disarm your quadcopter first.


To navigate through menu in the OSD:

  • PITCH/ROLL sticks are used to navigate
  • YAW stick is used to adjust / change values

OSD Menu Index:

  • PID Config (Roll/Pitch/Yaw PID for many flight modes)
  • RC Tuning (RC Rate, RC Expo, Pitch/Roll Rate, Yaw Rate, TPA (Throttle PID Att)
  • Voltage (Display voltage on/off, Adjust Voltage, Voltage alarm, Cells)
  • RSSI (Display RSSI on/off etc)
  • Current (Display Amp on/off, Adjust Amps)
  • Advanced (Unit – Metric or Imperial, Signal – Pal or NTSC, Mag Calibration)
  • Display (On/Off switches for Horizon, Sidebars, Scrolling bars, Throttle, GPS Coordinates, Sensors, Gimbal, Map Mode)
  • Statistics (Trip, Maximum Distance, Max Altitude, Max Speed, Flying time)

Firmware Flash

Some sellers of MinimOSD flash the latest firmware for you, so you don’t need to mess with the firmware flashing. But there are times when you want to update to the latest firmware, or want to try a different firmware. To check what version of firmware you currently running, hook up the OSD to your quad, you should see version number on start up screen.

It’s described in great detail how to flash OSD firmware on each firmware project page. Here is a summary what I did.

  • Download firmware files.
  • Donwload Arduino IDE
  • Open firmware files with Arduino IDE
  • Change config tab to your needs
    • I didn’t change much, only Type of Hardware (WitespyV1.1) and Flight controller firmware (Cleanflight)
    • mw-osd-arduino-config-hardware-type-fc-firmware-minimosd
  • Connect FTDI programmer to MinimOSD / Micro MinimOSD
  • Compile and Upload sketch

Leave a Comment

By using this form, you agree with the storage and handling of your data by this website. Note that all comments are held for moderation before appearing.


Jerico A. Parazo 2nd June 2023 - 3:06 am

Hi there. You site has been helpful with drones. I am curious if this will work with an Inav FC?

Oscar 2nd June 2023 - 9:34 am

Most modern fc comes with OSD capability so you don’t need the MinimOSD anymore, for example matek f411 wte:

Chaitanya Singh 6th February 2019 - 4:06 pm

Hi Oscar,
I am using a pwm receiver, so how do I plug the rssi wire?
I am using a FlySky fs-r6b
Please help!

jeremy lodewyck 21st July 2018 - 3:43 pm

For those getting the error “avrdude: stk500_getsync(): not in sync: resp=0x00” all you need to do is pull the 5v pin while it compiles the sketch, then when it starts to upload, plug it back in.

This is because there is no RESET on the Micro Minimosd, therefore it needs a manual reset to communicate at the moment of uploading.



Claudio 16th June 2018 - 12:34 pm

Hi Oscar,
you wrote about Arduino UNO and its error: avrdude: stk500_getsync(): not in sync: resp=0x00 and I can confirm this, but do you know that the cheaper arduino nano v3 is perfectly working?
Just in the case you didn’t know ;-)

Carlos Basauri 20th March 2018 - 8:55 am

Hi Oscar,
I’ve read the comments and tried in forums and it looks like nobody has a ever faced a riddle like mine with a Micro MinimOSD. I thought you might have a clue. The story goes like this:
So I got this Kingkong GT90 and it is great fun, but comes with no OSD so I banggooded a Micro MinimOSD, and it works perfectly fine until I unplug the battery. When I plug it in again then all the values for batt voltage, etc. are Zero. To get proper readings again I have to log into the MWOSD configurator again.

I suspect it’s something related with the serial pass through (serialpassthrough 2 115200) I used to get into the MWOSD configurator. When I power cycle, somehow it looks like the FC cannot send data to the OSD…

As for the wiring, nothing fancy there. OSD wired into UART3, All wired correctly I guess: (+ to +), (GND to GND), (RX to TX) and (TX to RX), plus another GND running from the PDB’s 5V BEC. I soldered but finally cut the wire to the 5V input as it did not seem necessary. I haven´t wired either directly the batt and the OSD and I am using the FC values for batt voltage in the MSOSD configurator.

As for the setup, I am using a KingKong GT90 FPV racer, so the FC is the KINGKONG F3 Lite 6DOF, I guess it must be some version of the SPRacingF3. Firmware is Betaflight 3.3.0 and the FC runs with firmware released on 3/2/2018. I flashed the OSD`s firmware with a USB serial converter and it is running the one version you can download in the website (I think it is R1.7)

The problem goes like this: Betaflight COM port will not connect through the USB unless batt is unpluged. Once Betaflight is connected, batt can be plugged in to test radio, motors, etc. For some reason (don’t know why), I have to power cycle the thing to get into the MWOSD configurator. To connect to the MWOSD configurator batt must be plugged in because CAM, VTX and OSD (and TX) are fed by the batt and not through the USB. OSD LEDs do not light unless batt is plugged in.

With the computer plugged, after logging into the MWOSD cofigurator, I get the readings right. If I unplug the USB, the readings are still there all right, but TX-RX will not work, don`t know why. (I am using a SBUS plugged into UART2 for the RX). If I unplug the battery, and plug it in back again, RX now works normal, but the OSD (although the display is still there) has lost all the data and reads Zeros for all values…

Don´t know what to do next. I think I will wire the OSD to the batt to see if I can get at least battery voltage readings. The other thing I can think of is flashing new (older) firmware into the OSD if I can find it, though I am not very keen of unsoldering everything and putting it altogether back again.

By the way. Great job! Yours is the best mini quads website in aaaaaall the web

Mike 2nd January 2018 - 12:20 am

Hi Oscar what would be my issue with not being able to go into the menu with the sticks? I see the boot logo when I power up but when I put the sticks in position (throttle middle, yaw right, pitch forward) nothing happens I’ve also tried yaw left but still nothing, also on my fpv feed the word DISARMED alternates to NO DATA does this mean there is no communication to the board? I’m running betaflight 3.1.6 on a naze32, do I need to make any changes in the ports tab on the betaflight GUI? any help will be appreciated thanks.

george dimos 30th October 2017 - 5:39 pm

hello i am George , i am a paramotor pilot and i have no idea from drones and i need a help if its not a truble
i wand to make a helmet video screen with the inflight data like elevation, compas, speed etc. please if you can show me a setup and what parts do i need
thanks a lot

Zzubbione 17th July 2017 - 12:34 pm

Hello !
Frenchie user here, excuse my english… I have a problem with my micro minimosd.
I wired all the thing vy following this wonderfull tutorial (many thanks, Oscar !), And it’s absolutely perfect and fonctional!
But… Some brownout appears when my lipo voltage drop normally, and fly agressive. (Like a throttle punch after 2min of flying)
I use the micro minimosd on a nano brushless racer, kingkong90gt, powered with 2s.
I use a “dedicated” port to power the osd, and its on a little f3 6dof clone flight controler…
I manage to power the osd directly by the 5v supply of my vtx (eachine atx03)… Good or not?

Oscar 24th July 2017 - 3:38 pm

it should be okay in terms of current draw. Try that, if you are getting some noise in the video, or text disappearing, that could be because the MinimOSD is extremely sensitive to power noise, so I would recommend installing a small LC filter or capacitor at the power to the VTX.

Robert Moller 11th July 2017 - 11:26 am

where can i buy a FTDI programmer ?

Oscar 12th July 2017 - 4:13 pm

Yes, for example this one.

Freeman 12th June 2017 - 12:14 pm


I recently got a Micro minimosd and try to test it with a simple system.
I just used 5V BEC, LC Filter, Camera (Foxeer Arrow), VTX and OSD. Everything it connected to +5V and it works great without the OSD (I get the image in my goggles).
The problem is, when I connect the OSD, I get no signal any more. I tried to flash it to the latest MWOSD and KISS OSD, everytime the same problem, no signal. I noticed that the onboard chip is getting very hot, but that’s probably not an issue.

I’d like to know if the OSD is supposed to work even if I don’t connect any flight controller on it (on TX/RX pads), or not ? Shouldn’t it display at least the original video ?


D17E 16th February 2017 - 5:34 pm

hi oscar…
i got problem with my minimosd, thats not shown battery voltage anymore…
i flash it with 1.5.1 and 1.6.0 its the same problem with my SPR F3 running inav 1.5.1

please your advices oscar.

edward mcathey 27th January 2017 - 1:48 am

hi oscar,
really interesting forum,ive been through all the posts and have not came upon my problem,
first time ive used a naze32v6
i have 2 osds the mimim and the micro minim,
ive configured both using the mwosd v1.16 both connect and are can be setup in the mwosd gui,
the problem is im getting video overlay with both but i cant any data,
ive tried connecting to the tx and rx in the centre of the board and taking ground and power from the esc pins,
ive tried setting up a soft serial port but i cant find any simple explanation on the net as to how to actually configure the ports in cleanflight,
been trying for a few days now really need help desperately,actually tried osd on a multiwii and the osd works attitude control and everything else thats set up but cant get it working on the naze 32v6 ,
any help really appreciated

Leagle 23rd January 2017 - 11:16 pm

Hi Oscar:

Thanks very much for the info, as always. Two questions:

1) I am using a Pixracer APM that is powered by a power module, which feeds current and voltage information directly into the Pixracer; I’m using a receiver that passes RSSI into the Pixracer via a CPPM channel. Does this mean I don’t need to connect the battery or receiver directly to the micro minimosd? (i.e. can I just power the osd from the Pixracer and take the data from the Pixracer?)

2) I am powering both the camera and Vtx directly from a branched 12v connection to the battery; does this mean I don’t need to connect a ground wire to the osd with the video signal wires (on input and output of the osd)?

Mark 1st January 2017 - 11:34 pm

Hi and a Happy New Year to all

Right, here goes, first post for help……

Just connected up my first Micro MinimOSB onto my quad and am getting the display in my goggles covered in VVVVVV’s (image from camera is still there too and looks OK) except for two small areas approx 2/3rds of the way down that appear to be scrolling through a 3 letter/number code

Have checked & double checked all connections and all appear correct and everything else on the quad responds as expected (was flying fine before and goggles OK too)

Running: Naze 32 v6 acro, Frsky V8FR-II receiver (on PWM), 3 cell LiPo, 600tvl Sony board camera

Any suggestions as what my problem may be would be most appreciated ??

Jeremiah Davis 15th January 2017 - 2:11 pm

You need to upload the fonts.

Paul M 1st December 2016 - 3:34 pm

Does the new version of cleanflight eliminate the need for a ftdi programmer for micro minosd. If s o how possible when rx/TX for osd on naze32 cannot be connected when using USB.

Brad 7th November 2016 - 4:15 am

I’ve got a zmr250 with naze32 rev6b and micro minimosd. My problem is that the low voltage keeps blinking on my fpv screen. I’m using the VBat pins to the naze to monitor the 3s lipo. I’ve got the “use FC for battery” on osd checked. Voltage is correct on the screen and I have 3.5V per cell for alarm set on Naze. Why is the osd flashing low voltage on the screen?

Oscar 15th November 2016 - 5:47 pm

is your battery cell set correctly? (3S, not 4S)

I. Sotelo 25th October 2016 - 4:02 am

I installed the MinimOSD and everything works, accept the video image is inverted with respect to the text. I didn’t see any code or options in the GUI to adjust this. Any advice?

TheTri 1st November 2016 - 7:39 pm

The camera may be upside down.

steve bowen 4th October 2016 - 4:11 pm

I have three different kvteam micro osd boards at this point.
I have the same issue as many with the multiwii gui (cant get it to run on windows 10)
thus the kvteam boards
when I upload the program with Arduino all appears fine the upload starts and completes normally
when I try to upload fonts with the KVteam GUI that also appears to work fine
however when I change the paramaters in the KVteam GUI and try to save these it fails and never saves them
any help form anyone on this would be most greatly appreciated

GJ 30th September 2016 - 4:07 am

Hi Oscar,
First of all many thanks, this place is a a wealth of information !

I have a problem with getting this OSD working properly though,
Struggling with this for weeks now and I’m getting desperate.
I have a ZMR250 and use the PDB, (I know, I shouldn’t…)
ANY power I used from the board was to dirty for my video, I had a lot of interference from the motors and also had constant “blackouts” on the Micro MinimOSD (rebooting) when the motors started up. (OSD powered from the SPR f3)
I have tried a load of different filters without any satisfying result.
Also I must have tried EVERY possible wiring scenario I could find and swapped/removed/added GND’s everywhere.

What I came up with is to feed the video side of things from the balance plug on my 3S battery. I now have nice clean video so that works.
Also the OSD I powered from it’s own power supply (Pololu) to prevent the OSD cutting out.
Perfect, it all works, for about 5 minutes on the bench, and then…. “no data ” from my Flight controller.
It has killed the UART on two SP Racing F3 controllers thus far. No connection to Cleanflight possible anymore.
As you would understand, I don’t want to wreck my third FC that’s on the way.
Any suggestions are very welcome !
Please find the connection diagram here:
So my controller is fed from the PDB BEC, my LED’s from a ESC bec, and the OSD from the Pololu.

Oscar 3rd October 2016 - 4:06 pm

you are missing a GND between FC and OSD :) but that diagram looks okay to me apart from that.

Gabriel 22nd September 2016 - 3:34 pm

HI to all!!

Oscar this site is like heaven!

My answer is simple, What do I need to display AMPs?

Oscar 23rd September 2016 - 3:26 pm

you need a current sensor, and the signal output of current sensor goes to the MinimOSD (CURR) pin.

Mel 19th March 2017 - 11:58 am

What type of current sensor would be ideal?

Martin Cloutier 17th September 2016 - 3:58 pm

Very good article.
I’ve read a lot about Micro MinimOSD but the information is different from one site to another.
I need to know what kind of current sensor I need.
Do I need a current sensor that outputs 0.0 – 3.3V or one that outputs 0.0 – 5.0V.

Oscar 19th September 2016 - 3:38 pm

both should work since minimOSD runs on 5V, you probably just need to calibrate it base on the signal voltage level differences.

Dariusz 10th August 2016 - 4:50 pm


Just wired the RMRC micro minim (mw firm) to my SP Racing F3 board. I want to display voltage and be able to adjust rates. Do I need to hook it up to a computer to set it up? I was hoping to change the config via the OSD menu. However, I cannot enter it. It seems there is no connection to the FC because OSD still states disarmed once I arm. I suppose I can try wiring to the other set of TxRx pins on the SP Racing board..
Second issue rendering this setup completely useless is that voltage reads 0.0. My follow up to this will be wiring to the batt2 pin instead of the current batt1.

Any feedback will be greatly appreciated. Biggest question is whether I can set it up without the ftdi/usb route.


Dariusz 16th August 2016 - 3:13 am

OK so in case someone else is looking for answers I was, here’s the fix to the above issues:

Answer to the biggest question: a USB connection between the micro minim OSD and a computer is not required to set this up and running.
If OSD is working and menu cannot be entered the issue is with the TXRX wiring. TX must go to RX and RX must go to TX. Voilla! This will conflict with the USB to FC connection and certain things like ESC calibration will not be possible. No problem. Desolder the TX RX wires on the FC to the other set (UART3) and activate it in Cleanlight (Betaflight) in the Ports section. You will know right away if it is working because the OSD welcome screen will display fc firmare version. If it is showing 0.0 version, it is not connected to the FC properly. Voltage issue I was able to resolve, but in a weird way. I could not get the voltage to read other than 0.0 when wired to batt1. So I wired the battery to batt2 and it seems the OSD reads this as video voltage which you can select to display by going into the OSD menu and changing the voltage display setting. No biggie. OSD displays a tiny VID icon next to it. Who cares.

Hope this is helpful!

Anthony 3rd September 2016 - 3:10 am

Man thanks so much! Was about to de-solder my minimosd and reconfigure until I read this. Swapped the TX and RX wires on my FC and it worked like magic!

Jeff 9th August 2016 - 1:59 pm

Hi Oscar

I have a maze 32 10dof rev6 and cannot get the rssi to display correctly, I tried just about every configuration possible to no avail.
Do I have to change anything in the mw1.6 arduino sketch?
My friend is trying to get it going as well, no luck.
I want to use flight controller for rssi, I have given I a channel on my taranis and set clean flight to ch7 on receiver tab but, nothing all I’m getting is 100%, 50% or 0%.
Any ideas where I’m going wrong ??



artur 22nd July 2016 - 9:49 pm

hi oscar. i realy need ur help
i have fc spracingf3 and microminimosd w kvmod. i use socket for uart 1 left from usb socket (up not the bottom ones).
only wiring from this socket to osd. and 1 wire vid from cam in osd adn 1 wire vid to tx in v.out pad microminim osd. why always waitinh mavlink hearts beats ?
thankyou for your help. im waiting.
from indonesia

Oscar 24th July 2016 - 2:27 pm

did you install the correct firmware on the MinimOSD? you should get MWOSD.

Ronald 18th August 2016 - 5:02 am

Hi oscar, i just instaled micro osd, in 4minute, the osd got hot, is that normal?

Oscar 22nd August 2016 - 2:56 pm

yes it’s normal, minimOSD gets hot.

Darryn 16th July 2016 - 5:31 pm


Firstly – Love your articles, they’ve made my life a lot easier – everything I need in one place.

Secondly – Do I still connect my Naze32 to the battery so that logs the battery voltage or is this passed through via Minimosd?

Cheers in advance

Oscar 17th July 2016 - 4:00 pm

Hi Darryn,
thanks :) Yes it’s still preferable to connect battery to the VBAT pins on Flight controller rather than MinimOSD, so you get buzzer voltage warning.
Unless you are using the OSD as a standalone OSD (no TX/RX connected to FC) then you should connect VBAT on OSD.

Flo 3rd July 2016 - 6:25 pm

Hey there,

had the Problem of the OSD loosing the HUD throttling up. The “common ground”- option didn´t work for me.
Here might be another option to solve that problem. I Took the +5V out from my VTX to power the osd. Helped a lot. No more “image jittering” and stable HUD for the whole flight.
Cheers and thanks for the help to OL.

Irwin ng 30th July 2016 - 7:06 pm

Hi, would like to know which pin u connect to power up the osd board with 5v. Is that the 5v 500mah pin or the pin along with rx tx? Thanks in advance

Oscar 7th August 2016 - 2:26 pm

use the 5V 500ma one if you can. I have also used the other 5V input which hasn’t been a problem for me.

Aki 1st July 2016 - 1:15 pm

Hi Oscar,

I am using the BrOSD chip that stacks with the Naze 32 FC. You rightly mentioned that the roll, pitch and yaw rates cannot be changed in the OSD because the roll and pitch are one in the OSD while the 3 are different in the the FC. Is there anyway then in later versions that the rates can be set in the OSD ? The multiwii version in BROSD I believe is 2.3.1. Pls help.

GODsaveTHEcat 28th June 2016 - 6:26 am

Hi. This is a great tutorial. Unfortunately I have a problem, my Micro MinimOSD is showing some jibrish, whole screen is filled with letter v and some Chinese signs. I flashed it with newest software using Arduino IDE 1.0 (newest version didn’t want to flash it because of low space) and set it up with MW-OSD GUI few times but I still cant make it work wit Naze32 Rev6.
Here is a photo of my screen

Herman Sugianto 28th June 2016 - 1:00 pm

Your font.. you need to upload the font..

Alfonz 21st June 2016 - 11:32 am

Hi there,
I assume it could be used for any rc plane not only quad right? I want to use it for my bixler. I just need speed, altitude and position indication.

Oscar 30th June 2016 - 1:15 pm

you can use it on anything, but only voltage and timer (maybe rssi and current as well)..
i am not sure if you can with GPS data, the MWOSD firmware can only understand protocol from Cleanflight/Baseflight firmware i think…

Ben 23rd May 2016 - 10:02 pm

So any help is appreciated here. In a nutshell, my micro minimosd for whatever reason cannot detect my battery voltage.
I can get into the osd menu fine and when I arm my quadcopter it says its armed on the osd but it always says my bat voltage is 0.0v. Ive tried different pads on my pdb and also swapping betweeb bat 1 and 2 on the osd but nothing works…

Oscar 24th May 2016 - 12:00 pm

make sure the “use FC voltage” settings in GUI is not selected?

Ben 24th May 2016 - 9:33 pm

Haha that was it! I literally couldn’t find the answer to my problem on any forum so thanks a bunch

bruno 29th July 2016 - 9:32 pm

Hi there,

In my case is the oposite. My FC does not have voltage sensor and I need from OSD, so I did nos mark FC voltage.

So I plugged Bat on Bat1 (and checked with voltimeter as well), but the OSD just displays 0.0 from battery.

I also checked that is no video voltage and voltage adjust is around 110…

Please, any clues?


Jonny 18th May 2016 - 12:06 am

Hi I got the osd working but the screen is full of characters so I can’t see past it. What could this be?

Oscar 24th May 2016 - 10:45 am Reply
Herman Sugianto 28th June 2016 - 1:02 pm

Sane problem.. you need to upload the font..

Martin 8th May 2016 - 2:20 am

Hi Oscar,

I am building my first 250 quad for fpv racing. I have a question. I am powering my vtx and cam directly from 3s lipo, using lc filter in between. Since micro minimosd need 5v input, should I power the osd using 5v from the cc3d (withour lc filter), or use separate step down circuit from the lc filter then to the 5v pin, or should I connect both? Thanks!

Chris 11th May 2016 - 4:19 pm

I have the same problem and no space to spare so was thinking I would put the lc filter in front of the 5v bec so I would only have bec noise hopefully there wont be much!

Truls 7th April 2016 - 4:39 pm

Hey Oscar. I’m having a problem with my Micro MinimOSD where I receive some data from the FC but I can’t write to it. If I make a change in the menu it won’t be saved. Also even though having set up vbat correctly (shows the right voltage in cleanflight), but it won’t show up on the OSD.

Any idea what might be the problem?

sam 5th April 2016 - 9:22 pm

Hi Oscar,
would be possible to post a diagram on connecting MinimOSD to Naze32 V6 Please?

Josh Mor 5th April 2016 - 5:52 pm

Hi, Oscar
I just install a CC3d with Micro Minim OSD with MW OSD software, but I only use Open Pilot to configure the Flight Controller, And I Have two problem, first My Screen only show Disarmed status, the flight time and the flight Mode. There is no Horizontal Line and also show No Data alert.
The other problem is my video signal is in Black and White not in color.

I think my problem is I used Open Pilot and I should change to Clean Flight to program the CC3D.
Am I correct?


Bogdan B 28th March 2016 - 5:53 am

Hi Oscar,

Really helpful article! I have one question. What kind of current sensor can you use with the MicroOSD? I have an APM2.5 90A Current sensor, but from what I understand that uses 5v for scaling, while MicroOSD uses 3.3v?

Should I try to hook it up?


Oscar 30th March 2016 - 5:35 pm

try to scale down the voltaeg with voltage divider… then play around with the scaling factor to tune accuracy.

Juan David Barrada 15th March 2016 - 2:10 am

Hi Oscar!

I’m planning to use either, the Micro or Minimosd, in my ZMR250 which is my first drone and therefore my “learning-drone” but I still have too many doubts.

The main, and please forgive me if the answer is very obvious, but if I connect my OSD to my naze32 “Acro” version, not having this one nor a magnetometer and nor a Barometer as the full version does, what information would i get on my screen? (Or better yet: What is the information I’m not going to get on my screen since this is the naze 32 “Acro” version?) Do you think I should better change the FC for the full version?

Thanks in advance for your help and your responses.


Wolfman2 14th March 2016 - 7:55 am

Hi Oskar – I got the Iluminati FC.That thing is pretty new and not much is known about it so i am collecting info wherever i can.I just connected a GPS (NEO) and everything works fine exept the OSD.There is no indication about the number of sattelites – nor is there the HOME arrow or distance to home.Nothing GPS related shows in the OSD.I am using different version of the KV Team OSD program but the Iluminati is not accepting any changes (Com 8) Is there a way to flash something else into that thing without starting at 0 with all the Arduino stuff ? Any other OSD known to work well in that type of FC ?? Thanks for the help – greetings – wolf

Wolfman2 14th March 2016 - 2:51 pm

I forgot – the Iluminati connects via USB to the PC and there are switches on top so you can either fly (1+2) wotk with the OSD (3+4) or wotk with cleanflight (5+6) If i am in cleanflight mode i cans ee that i get a whole bunch of sattelites but i cannot make them visible in the OSD. Does Minim OSD can show info about that – about “home” direction – about distance to home ? I think yes but why cant i change anything in my OSD when i start KV Team OSD ? I can upload new fonts to the Iluminati but whatever else i change will not end up in my FC .I can see SATS in one corner but there are just lines behind like this SATS –:– I am totally lost in this -thanks for any help you can provide – greetings — wolf

Bludz 24th March 2016 - 10:52 pm

Hi Wolfman2,
I’m also trying to understand this FC. Think they called it Illuminati because there isn’t much known about it and the people behind it keep it a secret.
I’m not trying to get a GPS to work on mine but I read your post and thought perhaps I could help. With mine, you don’t get all the data displaying on the osd unless you have it ‘Fly’ mode. I don’t get a fake horizon unless it’s in ‘Fly’ mode. Reading your bit about the dipp switches suggests you know what I mean by ‘Fly’ mode. However, the way you describe how they work is different to how I use it. The only info I could find on the dipp switches was by looking at the FC that the Illuminati looks to be a clone of, the OZE32. With the Illuminati case on, the dipp switches are upside down (ON is on the bottom and upside down). So looking at it the right way round (ON at the top written the right way up) I have to have 3,4,5 and 6 on/up and 1 and 2 off/down to get the osd to work and the quad to fly. This is ‘Fly Mode’. Then to use cleanflight I have to put switch 3 and 4 to off/down. Looking at the info on OZE32 dipp switches is where I got this combination, it also says that you have 1 and 2 on/up with the rest off/down to use osd mode.
Where did you get your info on the dipp switches? Maybe I’ve been doing it wrong all along and should use them as you say. My only issue (only not to be taken lightly as it’s pissing me off) is that when I throttle up, the osd overlay vanishes and then when I cut throttle it returns. Any ideas on how to solve this?

Bludz 25th March 2016 - 10:28 am

I have now solved my issue with the screen disappearing. I had the vtx powered by the balance lead, and the osd powered with the FC by a 5v out on my PDB. After reading above that this could be solved by using a common ground for vtx/osd and cam, I rewired the vtx to be powered from the PDB so they are all using the same power and ground. This has worked a treat and the overlay no longer disappears.
While playing around I entered the osd menu within the overlay (Throttle 50%, yaw full right and pitch full forward). I noticed that there are options in there for satellites and gps stuff but I don’t run one so I don’t totally understand what they are for but thought it might help.

Martin 13th March 2016 - 9:28 am

Hi Oscar,

I am newbie in this hobby and still learning alot. Your blog has very good resource for me to learn. I have questions, what is the max voltage supported by the bat1 and bat2 pin? Do I need voltage divider to lower the lipo voltage before connecting to these pins? Thanks.

Oscar 14th March 2016 - 4:41 pm

I am using 4S and I can connect directly to these pins, no need for voltage divider.

Brian 5th April 2016 - 12:06 am

Mico MinimOSD can measure up to 6S. Check out these on Amazon, they show it in their literature/

Angel 11th September 2016 - 12:23 am

I’m using 4s when I test with a lipo at storage voltage (3.8v cell) the HUD shows but if I use a fully charged one it does not show, does anybody has an idea?

seth 6th March 2016 - 2:09 am

ok i know that the osd level pitch line set for craft level…but is there a way to get the osd to let there be more then 15 degree of pitch…the pitch line stops moving about 15 degs.. i want to know what 45 degs. is when im in there a way to do this??
And the altitude is not jumps all over the place?

bubu12 3rd March 2016 - 1:48 pm

I can be programmed via the COM port on my computer?
Do I have to buy this programmer FTDI?

Herman Sugianto 28th June 2016 - 1:06 pm

No.. you can’t.. you certainly need ftdi break out. There is no usb connector in minimosd or the micro ..

neB 6th July 2016 - 1:40 pm

Actually there is a USB connector for a MiniOsd that is integrated to a power distribution board.
This is really very handy and makes it easy to just plug to your usb and program/modify

Zborecque 19th February 2016 - 12:59 pm

Does anyone know anything about some maximum resolution limits for the micro minimosd? My friend claims, that since his camera is 700/800TVL its somehow burning the micro minimosd. I have the exact same cam. I wouldn’t like to switch to a lower resolution. Somewhere in the internet I did read something, that micro minimosd works best with 576p. Is that true? Can I safely use my 800 camera with this OSD? Maybe my friend messed up the wires :)

Oscar 22nd February 2016 - 11:36 am

sorry to say that, but it sounds more like an user error to me :)
minimOSD should work with higher TVL camera… even 1200TVL was working fine… so 800 shouldn’t be a problem.

by the way, I recommend joining this forum, it’s very useful and there are lots of helpful people there. I am a daily user too :)

D 15th February 2016 - 9:45 am

Hi Oscar,

i have troubles with my micro minimosd. I have 2 of them with the samme issue… when i perform rolls/flips the OSD is disappearing/resetting/rebooting. All components are connected to the same ground. Also its not the same “disappearing”… When you dont connect everything to common ground the OSD is more like “vanishing”… In my case the whole OSD is like “resetting”… I get a grind of “+” (pluses) on the screen for ~0.5 seconds and then the OSD is back to normal. This sometimes occures when i perform a hard landing or on hard punch ups.
I am using MWOSD and Cleanflight 1.9/Betaflight2.3.4 and II have the same issue with 2 OSD boards on the different setups.

I would appreciate some hints because I can’t find anything regarding this behavior…

Kind Regards

Oscar 15th February 2016 - 4:15 pm

sounds to me it’s a power issue.
minimOsd is extremely sensitive to voltage changes. Do you use any LC filter or voltage regulator? if not you probably want to consider having one.
if you are already using one, and it’s shared with other components, you might want to use a standalone power source for it…

Nic Hume 15th February 2016 - 2:36 am

Hi Oscar,

I’m just working on installing my Micro MinimOSD and just soldered the pins on, and gave it a quick continuity test. Everything is fine EXCEPT my VideoIN seems to be shorted to the common ground.

There are no obvious screw-ups on the soldering (i.e. there are no obvious solder bridges created by me) … Does anyone have trouble-shooting ideas, or am I just dead in the water?

Florian 2nd February 2016 - 7:23 pm

Regarding the Mirco MinimOSD. Make sure to power the MinimOSD with additional 5v when updating the fonts.
The 5v from the FTDI alone won’t work.

On the normal MinimOSD make sure both sides of the board are powered.
The USB adapter must output 5V or more to reliably load fonts, 5V or under causes lots of problems. So use a powered USB hub or power from the flightcontroller or 5v BEC.


Rdemrem 16th January 2016 - 10:23 pm

Hi Oscar
With a 3S LIPO the OSD works great
When I plug a 4s LIPO the video is ok but the informations displayed are a bit flickering and not really stable, after one/2 minutes fly the OSD Infos just disappear from screen
An other indication if I disconnecte (still with a 4s) the camera the informations become clear and readable

I have two step down
One to power the naze32 and the osd with 5v
One to power the vtx and the camera iin 12v (my cam&vtx do not accept 4s)

All grounds are connected together
Any idea

Oscar 20th January 2016 - 11:09 am

i think that might be a unstable/insufficient 5V power for the OSD.
when you go on to 4S, your 5V regulator will get a lot hotter and might provide less output current than being on 3S…
and the OSD draws nearly 0.5A alone. try to get a better 5V regulator or dedicated 5V for it.

Francis 31st December 2015 - 12:58 am

Hi Oscar,

Im having problem with the osd. Im getting the osd overlay but no video camera. Its a 12v connected to a rc filter. I have tried to find out the problem but impossible to find answers. Can you help me out ?

Bryce 15th January 2016 - 12:31 pm

Have you tried toggling the OSD between NTSC and PAL in the OSD GUI menu?

Snowedt 30th December 2015 - 4:31 pm

Hi Oscar, thanks for all your helpful posts! I lean a lot reading your articles.

Do you know howI can get the rssi value out of the x4r? All the setup that you describe stays the same, micro minimosd, naze32 and I will try to flash betaflight.

Thanks for your help.

Oscar 6th January 2016 - 11:03 am Reply
Ian Jackson 29th December 2015 - 5:53 pm

Hi Oscar,

Further my last, it would appear to be in some sort of R/C based setup system….how do I get ut out?

Oscar 6th January 2016 - 11:01 am

sorry never heard or seen this problem… can you post a some pictures in my FB group?

Ian Jackson 29th December 2015 - 5:24 pm

Hi Oscar,

Just set up a Minim to work with CC3D….flashed firmware etc, plugged it in and hey presto – all good!
Then I picked it up and inadvertently pressed the button on the PCB….system rebooted and now only displays “System Setup – Link Active”.
I can’t get it to go back to normal OSD – have tried power cycle and even re flashed the firmware

Any ideas?

mrteak 28th December 2015 - 1:26 pm

Hi Oscar, How do i connect a minimosd to a TornadoFC?, not sure as to where the rx/tx get connected to from the minimosd

Oscar 6th January 2016 - 10:56 am

sorry i don’t have a tornado fc to show you :(

Andres 21st December 2015 - 8:31 pm

Hi Oscar Excellent post as always!

Question however slightly different setup..
I have my OSD setup such that TX and RX pads of the OSD are connected to pads 3 and 4 of my Naze32 FC.. I enabled the UART channels in Clean flight so that I can set and save my PIDs and RC rates via the OSD and RC transmitter. This works fine on one of my quads however on another quad with the same exact setup I can change and save PID setting but not my RC rates and expo. Further I noticed that the yaw rate in clean flight is mapped to the TPA in the OSD GUI.. So when I change the yaw rate in CF, that setting is applied to TPA field in the OSD.
Any idea why the PID rates can be configured via the OSD but not the RC (roll, pitch and yaw) and expo rates? Everything else works fine (voltage, PID set and save, etc.) and it works as desired on my other models.

Naze32 Rev6 (same problem with a rev 5) – Cleanflight 10.1
Latest Minim OSD firmware

Do you think this is an incompatibility between CF 10.1 and MWOSD R1.5?

Oscar 25th December 2015 - 6:49 pm

Hi yea it does sounds like a firmware issue. i have been using mwosd 1.4 and having good luck with latest betaflight, maybe try that?

austadt 10th March 2016 - 9:41 pm

this issue is probably because you have choosen wrong software in the scetch while flashing. Seen others with similar problems. Try reflashing firmware with correct flightcontroller software defined

Greg 6th December 2015 - 8:58 pm

thank you for this tuto

i try to move in pid menu but nothing happens..
i have a naze32 1.1.10 and mwosd r1.5
all is ok but stick movements dosen’t give any response…

hud is ok so communication between naze and minimosd is ok…
i have an orange sattelite, so ppm to input 4

can someone help me ?

Greg 7th December 2015 - 9:20 pm

i find a solution… i change this in def.h file :
#if defined SERIAL_SUM_PPM_GS //PITCH,YAW,THROTTLE,ROLL,AUX1,AUX2,AUX3,AUX4,8,9,10,11 //For Graupner/Spektrum
#define ROLLSTICK 0
#define PITCHSTICK 1
#define YAWSTICK 2

and now with these values it’s ok…

ALVIN 6th December 2015 - 7:21 am

Hi Guys,

Any solved thier issue with disappearing OSD overlay whrn throttling up?
I am having the same problem. My quad has a common ground… And since all the ground pad are connected to each other I only connected 1 ground of the OSD to quad’s common ground.

I am supplying the OSD from the PDB’s inbuilt step down voltage regulator.

Thanks and Reagards,

chris 2nd December 2015 - 8:16 am

Hi Oscar great tutorial thank you! However, do you have a schematic to add gps or does gps connect directly to the naze32?.

george 1st December 2015 - 1:53 pm

“But be aware that the computer connection uses the same serial port, that means if you want to use Baseflight, or Cleanflight configurator, you will have to disconnect the TX and RX from the OSD first.”

Thats why USB start to random disconnect , and when I hit save in configuration also got disconnects , I believe that there is a conflict with the OSD , I didn’t disconnect the OSD to test if the CC3D will work. is there any way to use USB and OSD simultaneously

Oscar 1st December 2015 - 5:08 pm

move your OSD TX/RX to UART2 (RC pin 3 and 4)

Riquez 28th December 2015 - 10:14 am

Hi Oscar, This is a great alternative, but in my case UART2 (pin4) is for SBUS. I guess there isn’t another option?

Justin 27th November 2015 - 8:12 am

Hi Oscar
Just wondering if the new version of cleanflight allows the pitch and roll rate to be changed via the osd menu? It would be good todo away with the bluetooth adapter

Oscar 27th November 2015 - 4:32 pm

i haven’t been using cleanflight, but betaflight, and it works fine.

Andrea 26th November 2015 - 6:32 am

Hi Oscar do you have a solutions for naze32 mini minimosd and screen character artifacts

Andrea 26th November 2015 - 8:27 am

Problem resolve sending the default font library by osd gui

Reuben Horner 22nd November 2015 - 12:37 am

Hi Oscar, what firmware should i use on my osd now that the KV team one is sort of abandoned?

Oscar 24th November 2015 - 5:46 pm

I am using MWOSD V1.4 and having great result with the cleanflight v1.10 and betaflight V2

Mike 12th November 2015 - 3:03 pm

Hi Oscar,

The soldering on your Micro MinimOSD is great! I had mine setup with the pins hanging out all different directions and after seeing your setup it hit me like a brick! I change the pins out and now it is beautiful and compact! I just wanted to say thanks!

Here is my before- and my after!-


Oscar 12th November 2015 - 3:31 pm

Fantastic Mike, looking really neat :D
I really like mine too, fits well in a compact 180 frame :)

Elixer 8th November 2015 - 10:21 pm

Hi Oscar

I have built and installed the OSD on 4 quads. 2 quads have no problems and are clear pictures. The other 2 OSD’s are giving me fits. As I throttle up, I get lots of distortion. I have tried putting filters in line and compositors in and none of these things have helped. Any ideas ?


Oscar 14th November 2015 - 8:34 pm

Not sure if that’s OSD related, have you tried testing it without OSD? (connecting camera directly to VTX).. maybe the noise is coming from somewhere… make sure you power all of your camera/VTX/OSD from a filtered power source also.

jaytherider 7th November 2015 - 1:27 pm

Hi Oscar,

I have a D4R-II and a micro minim OSD. This page was my bible for getting everything up and running, so thanks for it!
However, concerning RRSI: This is a digital PWM signal, and we need a low pass filter to connect it to the ADC on the OSD. So we convert digital to analog in order to convert it back to digital again. Strange, no? Why don’t they put a digital input on the ADC? Maybe other receivers output RSSI as an analog signal?


mrteak 7th November 2015 - 4:16 am

Hi Oscar, i just transfered my micro minimosd from one quad to another and connected it the same way i had on my first quad which everything worked fine, and now i am getting a flashing “no data” and it says disarm, i also am not getting voltage reading, i tried to go into the osd menu and it doesn’t work, not sure what i did wrong but i’m almost 100% that i hooked it up as in my other quad. Any info will be greatly appreciated, thanks.

usrbad 13th April 2016 - 7:08 am

Hi mrteak, did you solve the problem? I have the same problem.. tried to change tx/rx cable places but no success..

Peter B 2nd November 2015 - 3:12 pm

Hi Oscar

I am using a MinimOSD v1.1 board. I am using Video TX unit that takes a raw 12V input, has a regulated 300mAh, 5V output, and a 5V camera.
I note that the input voltage range on the analog side of the MinimOSD is posted with a picture of an older board as 5V to 12V.
Is there any penalty for attaching that regulated 5V to the analog side input pin? Will the regulator circuit on the analog side run any cooler not having to dump voltage from a 12V battery supply?

I do not want to link the analog supply voltage to the APM, but if I could reduce some noise by dropping the Vin from the APM, keeping the ground and powering the whole MinimOSD from the analog side via that regulated 5V, I might do that.

Peter B

Bottom line is that thing gets damn hot. It seems that with pre-regulated 5V from the analog side should let it run cooler.

Aurelio 31st October 2015 - 1:14 pm

Hi OSCAR. Great job.
I need help please. I have micro minim osd, cleanflight, and cc3d. It is connected in uart. Voltaje is read ok. But osd tell me that no has signal. I try to change tx and rx wired. But nothing happens. Un my club there are two people with same problem. Can you tell us how to connect cc3dd cleanflight and micro minim osd? Thanks

Oscar 14th November 2015 - 8:31 pm

sorry i don’t use CC3D only Naze32… but make sure you configured the port to be used as MSP at default baud rate?
also make sure you changed flight controller firmware to “cleanflight” in Config tab of MWOSD, before flash the minimOsd

eimis 25th October 2015 - 4:38 pm

Thanks for the info, Oscar, great as always bro. People like you who get others into hobbies are the real MVPs.

I’ve been trying to fix battery voltage not being sensed. Took me a while to realize my minimosd micro needs #define SWAPVOLTAGEPINS uncommented.

mike 24th October 2015 - 11:15 am

Hi Oscar

I have a MinimOSD flashed to 1.4 and a Naze32 running Cleanflight 1.9. For some reason I can’t get the main voltage to work. I have tried batt1 and batt2. The OSD always says 15.6 but when I pull the battery off the pins it still says 15.6v. I.e. it makes no difference. The only way I can get the main voltage is by using the one on the Cleanflight board. It’s almost like the whole board on the right hand side is not working.. However the OSD is great, heading etc…

Any ideas?



Efree 18th June 2016 - 2:39 am

Hey Mike I’m having that same problem with mine it seems like no matter what I do it still reads 15.6v did you ever figure out what was the problem?

brooks brucal 22nd October 2015 - 8:23 pm

Hi Oscar,

Can advice where to connect to supply battery if im using LC filter, is it before or after LC filter?Any effect to battery monitor reading if i connected it to after LC filter?


Keep it up.

Oscar 26th October 2015 - 11:48 am

What do you mean “before or after LC filter”? Are you talking about the voltage regulator?
if so, it doesn’t matter, both ways should work equally fine. I personally prefer to have it before the voltage regulator.

Mike 6th October 2015 - 4:52 am

Hi Oscar

Great article!! What do you recommend as best practice for shortening the provided terminated cables that come with the camera or the vtx? Should I bite the bullet and order the various PicoBlade and JST-SH terminals and pins so I can shorten the cables and re-crimp the appropriate terminals? Or is splicing a viable option?

For example the Aomway 200mw vtx came with a nice power and signal cable set with picoblade connectors – but the cables are 8-10 inches long and I only require 2-3 inches of cable on a 180mm quad.

Probably a rhetorical question but I thought I would ask. I haven’t found much discussion on the topic.



Oscar 6th October 2015 - 5:15 pm

just cut them to appropriate length i would say… on a mini quad they are just extra weight. Longer cables also not gets more interference (just my theory)

Simon 1st October 2015 - 5:24 pm

Great page, thanks helped me out a lot when I needed to flash my micro minim which had ArduCam 2.0 on it. I just could not get it to upload, then realized I needed to add the a cable between the DTR on the FTDI and the DTR on the Minim. Your bit about connecting DTR to the reset pin threw me for a minute.

Thanks again you are now bookmarked!

Solmag 26th September 2015 - 7:15 am

Hi Oscar,
I tried to load the KV_Team firmware to my MINIMOSD and I got a low memory message. This is the error message I got from arduino;

Arduino: 1.6.4 (Windows 8.1), Board: “Arduino Pro or Pro Mini, ATmega328 (5V, 16 MHz)”Sketch uses 25,206 bytes (82%) of program storage space. Maximum is 30,720 bytes.
Global variables use 1,669 bytes (81%) of dynamic memory, leaving 379 bytes for local variables. Maximum is 2,048 bytes.
Low memory available, stability problems may occur.
avrdude: ser_open(): can’t open device “\\.\COM1”: The system cannot find the file specified.
Problem uploading to board. See for suggestions. This report would have more information with
“Show verbose output during compilation”
enabled in File > Preferences

Giovanni 16th September 2015 - 3:56 pm

Hi Oscar
do you know why when i connect the battery plug on the batt1 and ground to ground my battery voltage result 0.0 v?
If i don’t connect anything it says 12.6 v but i think that it is a standard because it will not decrease. I have already try to adjust it by the voltage adjuster parameter but it doesn’t work. what can i do?

Oscar 16th September 2015 - 4:11 pm

can you try connecting it to Bat2 instead? i think there is a problem with wrongly labeled BAT1 and BAT2 in some minimOSD…

Giovanni 16th September 2015 - 5:23 pm

Hi Oscar
i solved it, you had to connect the battery on the batt2 pin because the batt1 pin is for vid voltage. :)

Giovanni 16th September 2015 - 5:23 pm

perfect thanks a lot!

Mike 12th September 2015 - 3:38 pm

“Hi Oscar” with everything wired up as per the diagram you provided I get no OSD overlay. After half a day of fiddling around I traced it back to some kind of issue with he RSSI output line from my D4r-ii setup in CPPM mode. With the OSD connected to channel 2 on the RX, no overlay. As soon as I disconnect it from the RX and reboot everything the overlay comes back.

Am I missing something? I don’t have my radio yet so the RX isn’t receiving any signal. Should that matter? You’d think the OSD would just read 0 for the RSSI if the RX wasn’t receiving any signal. I plan on running a T9x with a FRSky DIY kit.


Oscar 14th September 2015 - 3:31 pm

HI Mike, it could be an ground issue. Try connecting the GND on your RX or FC to the GND on the OSD I think that might sort it.
Alternatively, you can setup RSSI in one of your spare PPM channels, and read it off your TX/RX lines from FC. IMO it’s a better way of getting RSSI info.

mrgilchen 10th September 2015 - 10:32 pm

Hi Oscar,
I use Frsky D8R-XP with PPM. When connecting ch2 (rssi) to the Micro OSD I get no data and the FC wouldn’t work.
If I disconnect ch2 it’s all fine, but I dont get RSSI on screen.
Any idea?

Oscar 11th September 2015 - 3:13 pm

analogue RSSI doesn’t work very well, maybe you should try passing RSSI data in a PPM channel..

Sunil 28th August 2015 - 11:21 pm

Hi Oscars

I am new to fpv, and I am just wondering how power is given to the camera and transmitter. I do not see and power going from the OSD to the camera or transmitter. Do I just connect my camera and transmitter power to my power distribution board?

Thanks for you help

Oscar 30th August 2015 - 5:49 pm

Hi Sunil, Camera and VTX has their own V+ and GND, it’s not drawn in the diagram.
It depends on what your camera / VTX input voltage requirement is… for example both my VTX and Camera takes 12V, so i take a voltage regulator to get 12V from my 4S lipo (16V).

Sunil 30th August 2015 - 11:02 pm

Hi Oscar,
Thanks for your help. I will be plugging my camera and transmitter power and ground into my power distribution board. I am not sure that I need a voltage regulator since my power distribution boards have a spot for camera and transmitter.


Rob 28th August 2015 - 1:22 pm

Hi Oscar,

Great post, saved me a massive amount of time along with a lot of other stuff quad related. I’ve got the micro minim OSD, the V4R-II and a Flip32 and I simply cannot get RSSI to display on the OSD (running KV Mod OSD). I followed your instructions to the letter and tried loads of permutations of configuration but it won’t show anything other than 0% or 50% no matter what the status of the TX is – on or off.

What am I missing?

Oscar 30th August 2015 - 5:55 pm

Hi Rob,
Where are you getting the RSSI information from?
I found it’s best to get RSSI from a spare PPM channel, that way you don’t have to mess with low pass filter with the digital signal and such…

DavidM 19th August 2015 - 8:40 pm

Hi Oscar

I have the micro MinimOSD and everything works fine but the voltage. I have a connection to the battery and ground and I can adjust the reading from the OSD but it never changes with changing battery voltage. I have checked that it is connected to the battery voltage and not to a regulated source. Running MWOSD 1.4 with Cleanflight on a CC3D.

Oscar 20th August 2015 - 10:10 am

Hi David, are you getting voltage reading from your OSD, or FC? (what are you using to measure voltage)
If you are using the OSD, make sure “USE FC voltage” is unchecked?

Scot 21st August 2015 - 12:51 pm

Hi Oscar
Having the same issue. One of the voltages will not accept and adjustment and my fonts are seriously messed up. Ordering fdti adapter to hopefully fix this. This is my first minimosd too.

Paul 25th August 2015 - 4:09 pm

Hi Oscar

If you’re connecting battery voltage to the OSD board, you may have to connect to batt2. batt1 is for video – at least up to 1.3 and 1.4. 1.5 not sure if this was ever changed. If you’re using vbat from FC then yes you have to tick the option.

Soo 19th August 2015 - 12:34 pm

Hi Oscar
Always appreciate your helpful posts. Thank you.
When i tried to upload MW_OSD firmware th minimOSD v2, i got “stk500_recv(): programmer is not responding” message
and fail to flash.
But another minimOSD as same version, I have done flash MWOSD firmware.
How can i fix it? the first minimOSD was broken?

Oscar 20th August 2015 - 10:03 am

HI Soo,
well if the same connection and config works on one MinimOSD and not the other, sounds like an issue with that minimOSD? Yea might be broken.

bubu90 8th August 2015 - 4:39 pm

The avrdude: stk500_getsync(): not in sync: resp=0x00. issue means, that the pc can’t communicate with the atmel microprocessor. It can be fixed with choosing the Arduino Pro (5v, 16 mhz, atmega328) as the board you wish to program in the Arduino IDE. This way you can flash the OSD with your preferred firmware using an Uno (with the atmel chip removed) as an FTDI adapter.

Jerry 22nd July 2015 - 3:04 pm

no I tried 1.4 before 1.3 same results. using NAZE32 Full version with Minim ODS, alt, GPS, Speed, time,voltage. all other parameters are normal. Just my compass and attitude are bad.

Jerry 22nd July 2015 - 3:23 am

Hi Oscar, need help loaded Minim OSD with MWOSD R1.3 all indications are there but my compass and attitude are corrupted.
the attitude is displayed as w’s and n’s. the compass is shown as s’s, w’s, the attitude moves the letters change to other symbol’s not just a solid crossbar.

Oscar 22nd July 2015 - 12:18 pm

there is now version 1.4, try that first see if the issue’s been fixed?

Jerry 22nd July 2015 - 3:50 pm

not sure, bought it for my APM now trying to use it for my NAZE. MAVlink OSD

Jim 22nd July 2015 - 12:45 am

Hi Oscar

I appreciate all of the information you continue to share. Thanks for taking the time. Usually I can figure stuff out on my own with a lot of readying but I am stumped and hope you can help. I have this OSD running MinOPOSD with a CC3D. I have to use a different FW that supports UAVTalk. So I don’t get to use the configuration software you are using. I need help with the voltage math.

The setup menu includes 3 configurable settings: 1 related to voltage and 2 related to amperage. They are:

Measured Volt: 12.63v
Volt Div Ratio: 1149

Measured Amp: 59.29a
Amp Per Volt: 9900
Amp Offset: 5000

The measured values are not editable but the other three are. I did manage to change the VOLT DIV RATIO to a number that gives me a good value for a full battery…. but it stays there. For testing I have 2 used batteries. Both are 3s 2200mah with voltages of 11.5 and 9.1 (discharged it too low, I know). Both read 12.63v on the OSD.

Can you help me with determining what to set those numbers to?

Oscar 22nd July 2015 - 11:50 am

HI Jim
sorry i am not familiar with the system you are using. I main run Naze32 with MWOSD… from the sound of it, it seems your system is not picking up voltage at all and just gives a constant value?

Jim 22nd July 2015 - 12:41 pm

Hi Oscar,

It is receiving voltage. If I disconnect the battery the voltage indicator disappears completely, so it sees something. Just not sure what it uses to measure. I have found a couple of drawings showing folks using the B2 connection for battery and leaving B1 open. I may try that and see if it makes any difference.

kipikdur 19th July 2015 - 12:50 pm

To solve the problem of disappearance of the OSD when you go up the throttle!
We must connect the ground of vtx and camera to the ground of 5V micromosd?

Oscar 19th July 2015 - 8:58 pm

yes connect all VTX/Camera ground to OSD ground.

kipikdur 19th July 2015 - 11:38 am

Hi Oscar,
I have the OSD disappear problem when I give max throttle , Yet I have connected the ground on camera has ground on VTX in ground on MicromOsd. The weight that you speak is the ground of 5V
Thanx for the share :)

Danny 13th July 2015 - 6:21 am

Hi Oscar,

I’m trying to get my RSSI working on my minimumOSD and have my D4R setup as CPPM. Single wire from pin 2 to the microOSD RSSI pin. No dice… I’m getting something, 0 when transmitter is off and a value when on, but seems off from what is displayed on the taranis. Is this normal? What a good way to test?

Oscar 13th July 2015 - 10:19 am

if you go into the model setting on your taranis (1st or 2nd page of the setting can’t remember), there is a “Range” test, it basically reduces your transmitter module power to 1/30 so your RSSI will drop to 70% to 30% even very close to the receiver. Try that see if it works.

I have a feeling you just didn’t setup weight / offset correctly for input and mixer. check again:

niido 9th July 2015 - 9:23 pm

can i use this

as FTDI adapter?

Kert 12th August 2015 - 11:46 pm

I’d also like to know if I could use same kind of ftdi adapter.

Michael Morris 5th July 2015 - 10:05 am

Awsome article, One question, when I flash mine and i did a clear first i get a Low memory warning (with MWOSD 1.3 and 1.4) using the micro minim is this ok? or should i try something else

Oscar 7th July 2015 - 4:29 pm

what board did you select in Arduino IDE?

SAMUEL SU 1st July 2015 - 9:42 pm

Hello Oscar,

Firstly, i would like to thank you for all these helpful tutorials. Very informative and thorough.

I have the micro osd coming in and am very confused about voltage inputs and outputs.

1) will this micro osd accept 5v-12v input to power it up or just strictly 5v?
2) if 12v input is acceptable, will the Rx, Tx, and rssi tabs for telemtry also output 12v?
3) does it have a built in regulator to drop it down to 3.3v?

im just worried if i power this micro osd at 12v and connect rx/tx telemetry cables to the cc3d flight controller, the 12v ouput from the osd would fry my flight controller. is that even possible?

again, thank you,


Oscar 4th July 2015 - 12:11 pm

Hi Sam,
1) strictly 5V! you should power this OSD from your FC or ESC BEC
2) 12V isn’t acceptable for the micro
3) I don’t think it has a 3.3v regulator, but what do you need it for? if you need 3.3V just tap it from your balance lead :)

Samuel Su 13th July 2015 - 10:01 pm

Hello Oscar,

I have installed the micro osd and i dont get any text or osd on my goggles. i have connected everything correctly and am running 5v from the flexiport.

here is what im running:
-cc3d with cleanflight 1.9.0
-mrmosd with mwosd1.4.1

i have ppm enabled on cleanflight so i have pins1-3 for ground, power, and ppm.
i have also set flexiport (uart3) as “MSP” under telelmetry in Cleanflight GUI ports tab.
i have connected power (4.98v), ground, tx/rx to the osd from the flexiport. i have video running through osd and can see an image but no mwosd welcome screen. i would think even if i dont get any data in the osd, i would at least see the welcome screen on the video. but nothing.

should i connect the micro osd rx/tx to pins 4/5 on receiver port (also known as softserial in cleanflight)? or should i connect rx/tx from mainport (uart1)? i have msp data sending though vcp and mainport.

thank you,

Oscar 14th July 2015 - 11:15 am

you should at least see the overlay text and MinimOSD welcome screen at start up, even if your TX/RX is disconnected.
i think you should first look at why your OSD is not overlaying text on image first.

Oscar 16th July 2015 - 5:07 pm

also, try to disconnect the camera, and plug in the power, see if you get any text this time. If you do, that suggest you have chosen the wrong video encoding for the camera, you should switch between PAL/NTSC in MWOSD GUI.

Richard Gardner 29th June 2015 - 6:25 pm

Saw your comment about text fading on throttle up with the micro osd. Not sure i get the ground connections your referencing. Do you have a drawing or more details on the subject as i have the problem yiur describing

Oscar 1st July 2015 - 1:39 am

I meant to say, connect the ground on VTX to ground on minimosd, and ground on camera to ground on minimOsd as well.

Brett 19th June 2015 - 9:16 am

Hi Oscar,
hope you can help, I have to systems (openlrs – flip32+ OSD – cleanflight ) rssi works fine to OSD

scond system (DR4-II – flip32+ – OSD – cleanflight ) no mater what i try cant get rssi working, frsky set to PPM and tried rssi to OSD but just flicks back and forward 0-100-0-100% etc

if i set it up as Dj_Garfield said above my channel 8 on radio control is the knob that changes the rssi and not the rssi itself

measured the voltage from RX and its 3.16 tx off and .16 tx on

I thought the rssi out from rx and meant to be digital ?

all the best

Brett 19th June 2015 - 12:35 pm

After days/hours I have worked it out, like you say some of this stuff is very hard to find.
for me this is how i got it going

D4R-II in PPM mode – Flip32+ cleanflight with RSSI_ADC enable
RSSI from CH2 on rx goes to Ch2 on Flip32+ ( fine tune in OSD menu mine was 7-255 with 5v ref enable)
and you have to make up the PPMRSSI conditioner ( which is crazy with all the techo gear we got now) but it is very smooth and works great

help this help

Oscar 19th June 2015 - 1:08 pm

Glad you figure it out.

RSSI signal is PWM, to get the most accurate reading, i think you might need a low pass filter between RX and OSD/FC.
Here is a good example:

Brett 19th June 2015 - 10:59 pm

thanks Oscar

that was my main problem, I knew the rssi was PWM but to me the wave form it shows in the Frsky manual is digital so it through me off thinking i need the ADC enable in cleanflight

So why does the RSSI signal look like a digital wave form of square on and offs ?

Oscar 23rd June 2015 - 4:05 pm

PWM is digital, and it looks like on and off from a oscilloscope :)

Michael 15th June 2015 - 11:17 pm

Sorted my issue with telemetry…

FrSky telemetry and the MinimOSD use the same port (UART1) – disabling the minim’s port when telemetry is being sent…

Connected the frsky telemetry to SOFTSERIAL1 – working fine!

Oscar 16th June 2015 - 2:16 pm

aha! :)

Michael 14th June 2015 - 9:29 pm

My OSD text freezes when the quad is armed? So when I takeoff, battery voltage reads 12.6 and stays at 12.6, until I land and disarm, then it changes?

Is this what you were talking about connecting the ground from the video in/out feed?

Thanks, Michael

Michael 14th June 2015 - 9:29 pm

I’m using KV team OSD by the way ;)

Fernando Poitivin Goncalves 16th June 2015 - 12:52 am

Can it be that vou are having a conflict in naze32 com port between telemetry and OSD data ?

Oscar 16th June 2015 - 2:11 pm

the issue I was talking about is the total lost of OSD text… I have not come across issue you mentioned, can you try to connect ground anyway see if that fix it?

amolteni 27th May 2015 - 2:09 pm

I recently configured a MinimOSD with the latest MWOSD beta (KV OSD seems dead) , It was a little tricky but I found a useful trick to send the RSSI to the OSD if you have a Taranis X9D and a CPPM receiver such as D4R-II… without connecting the receiver to the OSD.
You have to configure a new Input channel on the Taranis that uses as source the RSSI signal coming from the receiver via telemetry, scale 100, weight 100
Then in the channel mixer configure a spare PPM channel (for instance channel 8) to use that Input as source, weight 200, offset -100.
After this you have the RSSI signal sent via CPPM to the Naze32.
In Cleanflight configure the RSSI function to use the channel 8 as source.
Then in the OSD Gui select the RSSI signal coming from the Flight controller. (I’m using the latest MWOSD beta).
You just need to adjust the range of the RSSI in the OSD Gui, 0 min, 255 max
And that’s it. Works like a charm in my configuration.

Oscar 28th May 2015 - 9:23 am

thanks amolteni for the tips :)
There are so many ways to configure these things ! :)

Steve Davies (Ddraig62SPD) 1st July 2015 - 11:39 pm

Hi Amolteni/Oscar,

I was unable to assign RSSI as the new channel source on my Taranis X9D running old firmware. I suspect that you either have an X9D with recent firmware or the X9D Plus model. Could you confirm?

Many thanks, Steve

Oscar 2nd July 2015 - 12:15 am

mine is on firmware 2.0.9 i think.

Steve Davies (Ddraig62SPD) 2nd July 2015 - 1:25 pm

Thx Oscar. I think I need to upgrade my X9D firmware to get the new features.

max ales 18th May 2015 - 6:41 pm

Where can I download last firmware?
thanx in advance

Kevin Yang 17th May 2015 - 6:21 pm

You art the man. I have learned So many things from you. Thank you very much.

Alberto 9th May 2015 - 6:23 pm

Hi! Great tutorial, but: Do you know if it’s compatible with the Flip32 10Dof from banggood?

Oscar 10th May 2015 - 1:25 am

yes, once you flash cleanflight that should work

Dj_Garfield 13th May 2015 - 2:03 pm

It works fine , I did it on a FLip32+ 10DOF , that Rox hard :)
I’m not aware of Rate mode flying yet , but I learn :)
The result is very clear , and the OSD is displayed up to the edge of the goggles LCD screen , and you have a wide area to see where you fly , instead of the MinimOSD Arducam FW .
If the MWOSD could work with MAVLINK protocol it would be great for my APM based UAV :)

dave 9th May 2015 - 12:41 pm

thanks for uploading this on youtube will be trying this out soon on miniquad just ordered parts.
as far as i know the vortex quad has something similar
this will be a great addition cant wait..

Dj_Garfield 6th May 2015 - 2:23 am

I had this behaviour , and I fixed it with powering the OSD in 5V from the Digital Side , and put the solder blob where they must be :) Read this at the section “Optional setup for critical cooling conditions” ,

Ed 3rd May 2015 - 5:46 am

If you have your battery connected to Naze32 for voltage reading then there is no need to fiddle with “voltage adjust”, just enable “Use MWii” and the OSD will automatically display the voltage detected by the FC. You will need to set the alarm voltage only.

Did you manage to have RSSI displayed without the PWM to Analog filter??

Oscar 6th May 2015 - 12:01 pm

HI Ed, yes good point, I should point that out, and combine the Frsky telemetry tutorial with this MinimOSD tutorial :)
but it also shows how to use the OSD directly for voltage monitoring…

Yes, the RSSI is connected directly to the OSD, no filter needed.

Dj_Garfield 3rd May 2015 - 12:10 am

Oscar , You must had full of work for this article : very technic , very clear , I will test this soon :)

Oscar 6th May 2015 - 11:57 am

thanks Garfield :)

Dj_Garfield 9th May 2015 - 12:08 pm

And This works fine :) I love mwOSD !!! all the informations fit in the screen while ExtraCopter FW cannot display at the edge of the screen so you have all the OSD display right in the middle of the video , and then you cannot see clearely where you fly :)
Thanx for the share :)

Dj_Garfield 3rd May 2015 - 12:08 am

Hy Shawn ,

Some clues to solve your issue :
If you power up your OSD via 12V regardless of 3S/4S it is possible that you experiencies the same behaviour than me , I solve this like that :
1/ I joint the analog and digital power by put the solder blob on the OSD ( depicted on the Doc of the OSD )
2/ power the MinimOSD via 5V from digital side of the OSD .
Since I made this , my OSD don’t desapear , I made a little video to show why the OSD freeze , in fact when you power the OSD with 12V ( analog side , where the video in and out take place ) , every time you ask throttle to voltage of the Pack fall down under 10V sometime , and the OSD freeze . As soon as you power the OSD with a 5V from a BEC you won’t have any problem , the OSD voltage must stay stable :)
If you don’t know where you have to put the solder blob :

Bill 29th August 2015 - 6:47 pm

Hi guys,
i have the same problem!! when i power up my whole system i had indications from the osd but i havent image from the camera. how i l power up my camera??

Shawn 2nd May 2015 - 11:42 am

i set mine up that way, also added grounds on the video leads per people’s suggestions based on my problem. My problem is that when I throttle up, my osd display disappears.

Have you had this problem?

Also, there is supposed to be a fix with a capacitor, but, I haven’t tried that yet.

Oscar 6th May 2015 - 10:06 am

no i have never had that problem… so added grounds for video in/out fixed yours?
could that be motor noise?

Oscar 18th May 2015 - 8:46 pm