ShikOfTheRa edited this page Apr 9, 2018 · 13 revisions

0 How do I troubleshoot connectivity issues

1 How do I use OSD / smart switch / Screen switching

  • There are 2 methods - using a RC channel (1-8) or by using OSD SWITCH if the FC supports it.
  • Select which method on the GUI
  • if using RC Channel, just make sure you use the correct channel. Numbering changed after 1.6

2 I have nothing on my display?

  • Ensure your cabling is correct
  • Ensure your PAL/NTSC OSD setting matches your camera setting. Using AUTO on 1.8 onwards is recommended
  • If using MinimOSD board make sure your output stage is properly powered.
  • Ensure you do not have blank screen layout selected
  • If using 3 way switch try different position
  • If using FRSKY or other high frequency RSSI, unplug until resolved.
  • Some stups require a consistent ground between camera and OSD video output
  • Check camera compatility documentation

3 Lines on my display are very feint and flickering at all times

  • This is usually a compatibility issue with the camera. Check camera compatility documentation
  • Use a large font file such as the one from ABL
  • Try increasing brightness and enabling fastpixel in config.h
  • if your camera is hi res (650TVL+) change camera CRT/LCD setting to LCD

4 I can't open GUI on my MAC - unidentified developer error / unable to open

5 I can't open GUI on my MAC - .app is damaged and can’t be opened

6 How do I setup a current sensor

  • The information is now updated in the calibration guide

7 My OSD turns off in flight / after powering up motors?

  • Ensure you have a good ground
  • Use a big cap (e.g. 3300uf) on the 5v supply to the OSD
  • Enable #define MAXSTALLDETECT in config or upgrade if not listed as an option

8 I get white glow effect/white streaks behind the osd text with Fatshark PilotHD

  • Set the following in config.h
  • #define FASTPIXEL

9 My voltage doesn't change during flight

  • Check you have selected the correct board in OSD HARDWARE settings
  • Check you have selected the correct battery option - FC if using FC connection
  • If using a micro board, you probably have to select RTFQMICRO
  • If using a full size witespy board you may have to select RTFQV1 in config.h
  • Ensure you are connected to the correct vbat pin some are reversed bat1 / bat2
  • Enable SWAPVOLTAGEPINS if you don't want to swap physical wires.

10 My Voltage/RSSI/Current does not change with adjusters

  • Note that adjusters are only for connections direct to OSD - NOT when connected via the controller

11 The OSD always shows NO DATA / DISARMED permanentlty and one or more other items do not work

  • This usually means the OSD is not getting information from the Flight Controller
  • Ensure your connections are correct. Especially tx/rx orientation
  • Makes sure you are using the correct baud rate - 115k is default
  • You cannot share serial with other devices like telemetry
  • Note it can be disabled in config.h
  • Baud rate in config.h MUST match baud rate in GUI (access via comsettings button)
  • Conectivity troubleshooting debug

BASEFLIGHT USERS - remove telemetry as follows:

  • feature -TELEMETRY

CLEANFLIGHT USERS - remove telemetry and enable GPS as follows:

  • feature -TELEMETRY
  • set serial_port_1_scenario = 5
  • set serial_port_2_scenario = 2
  • SAVE setting port 1 to 5 equates to MSP, CLI, GPS-PASSTHROUGH setting port 2 assigns it for gps , feature GPS will also need to be enabled

HARAKIRI USERS - ensure protocol set as follows:

  • tele_prot=0

12 The OSD always shows random characters on the NESW compass heading

  • This is typically a mismatch between the Flight controller type and the OSD controller selected in config.h
  • Latest version of OSD should correct for this

13 Data does not save when press write on the GUI.

  • If unable to update firmware, also check rx/tx connections are correct.
  • Ensure USB programmer provides correct voltage
  • Note some programmers have 3.3v/5v selection text swapped. Verify with a meter

14 I get garbage characters and / or font upload doesn't work.

  • Sounds like fonts need to be re-uploaded - but note:
  • For some of the original minim boards, the output stage (max chip) MUST be powered when uploading font. How depends upon your board / configuration
  • A programming voltage of 4.8v or higher is required.
  • Note some programmers have 3.3v/5v selection text swapped. Verify with a meter
  • Some stacked boards with USB connector also require vbat connected which powers the MAX chip and enables font upload
  • Programming with FC passthrough is not always successful.

15 I don't know if I should enable 5v ADC. When should I?

  • If using analog RSSI connected directly to OSD you must enable 5v ADC
  • If using a hardware Current sensor connected directly to OSD you must enable 5v ADC
  • If using more than 4 cells you must enable 5v ADC

16 Direction, distance and speed are not working

  • Normally the FC needs to be armed. Not applicable to GPS/FIXEDWING mode

17 I can't enter values into the GUI (Pre 1.6)

  • Click onto the box and drag up / down. Obvious eh ?!

18 I can't enter OSD menu

  • FULL RATES are required for the stick menus to be selected currently

19 How do I use MAP mode? It doesn't seem to work

  • Firstly items to be displayed need to be enabled in the hud layout being used. (Map Mode & Map Center)
  • Secondly - on the GUI or OSD menu, map mode buts be set from 1-4.
    • mode 1 is where aircraft is center and H displays home location
    • mode 2 is where Home is center of the map and X displays relative aircraft position
    • mode 3 is a combination of mode 2 and 3
    • mode 4 is low resolution, but with ^ indicating location of aircraft and heading

20 I get c:..... \java\javapath\javaw.exe unspecified error or javapath error. How do I fix it.

21 I get "Waiting FC” or "Waiting OSD". How do I fix it.

  • Ensure you are connected to the correct com port.
  • Ensure baud rate in GUI matches baud rate on the OSD
  • Ensure ONLY the OSD is connected to programmer. Disconnect other serial form OSD
  • Ensure TX/RX are connected the correct way
  • If using OSDOGE ensure switch is in correct position for programming
  • If using cheap OSDOGE/BROSD clone, disconnect board from the Naze32
  • Restart PC – especially if hibernated
  • Ensure physical connections are correct. Test by re-uploading MWOSD if necessary to verify
  • Upload EEPROM_Clear example sketch then re-upload MWOSD sketch.
  • Set serial port default value on PC to be same as OSD (e.g. device manager>ports>comx>port settings)
  • If using passthough, baud rate must match baudrate of FC

22 I get A screen full of error messages trying to load the GUI - inside the text is "Can't load AMD 64-bit .dll on a IA 32-bit platform"

  • You are probably trying to run 64 bit MWOSD GUI on a PC running 32 bit java
  • Try running 32 bit MWOSD GUI instead or change java to 64 bit version instead.

23 How do I configure for standalone GPS OSD (no controller)

23 GUI will not launch (Pre 1.6)

  • Try both 32 and 64 bit versions
  • Check other GUI FAQ points (therere a re several)
  • Completely uninstall all Java versions and re-install latest. Note you will have to google to find instructions to completely remove. As part of this, make sure path variables are completely erased before re-installing.

24 How do I use RSSI with FRSKY (D4R-II)

25 Display keeps blinking. May be worse at high throttle

  • This is noise on the power to the OSD. It needs to be sorted
  • Google LC power filter for FPV

26 GUI very slow to update / unable to turn simulator off (Pre 1.6 GUI)

  • Edit gui.cfg in GUI data folder
  • Set AutoSimulator to 0
  • Note it may also be a sign of an old pc or other application / malware running on PC

27 Can I swap between different batteries 3/4s and set alarms automatically 1.6/1/7

  • Use R1.6 and higher
  • uncomment AUTOCELL
  • Amend Woltage waring section in config.h as you require
  • Consider use of AUTOCELL_VOLTAGE

28 GUI is very slow to open up (pre 1.6)

  • Try disabling buetooth

29 MAVLINK / PIXHAWK / APM showing no data from FC

30 Unable to load MWOSD GUI configurator from the google chrome store

  • Unfortunately Google has not made its services available in your country. The following approach can be used to make it appear that you are in another country.
  • Download TunnelBear from the Google Chrome Store.
  • Launch the app and create an account.
  • You'll see the switch to turn TunnelBear on and a map of the world. Simply tap a tunnel anywhere on the globe (suggest US) and wait for the bear to tunnel its way there.
  • If you get a connection request, agree to it.
  • Once TunnelBear has created a connection to your new location, you can install MWOSD. Note : If the store still says it's not available in your country, you may have to clear clear the cache for the Chrome Note : Upgrades may require you to re-run TunnelBear

31 Can I use Paypal to pay for configurator

31 Unable to connect with GUI

  • Ensure you have correct baud rate set. Typically 56k for MAvlink/PX4/APM an 115k for all others
  • Try changing baud rate to something else then back again
  • Ensure nothing else connected at the same time
  • Disconnect OSD, reconnect and try closing and restarting APP
  • After launching app try waiting 30 seconds before clicking connect
  • Ensure TX/RX are connected correctly
  • If using passthrough, set baud rate to FC baud rate

32 Google chrome app version / PC app version / Google store close - what is the difference

  • For functionality there is no difference between the two
  • The same codebase is used. Simply different compiler to produce app
  • On chrome store the version is which supports 1.7 MWOSD
  • As google has announced closure of the chrome store we started to produce 1.7 and 1.8 versions of PC app ready to migrate users.
  • 95% of users were on Chrome – and the migration has started. ETA for completion Mid-April
  • Chrome users will start to see their apps upgrade to – this provides a key and instructions for enabling the transition to PC apps (and 1.8)
  • There is no cost to transfer or need to buy again 1.8.

Poor quality voltage supply can significantly impact the the reliability of your the system. This ranges from high voltage spikes that will cause your FC or OSD to fail completely to low voltage brownouts that will cause your FC or OSD to hang. All are bad, but all can be avoided. Regenerative / Braked ESC such as those using BLHeli / Damped light option contribute significantly to the issue. Systems with digital servos powered through the FC are also vulnerable.

It is important to provide a clean supply to your FC and OSD etc. Consider 5v and 12v connections (and also for FC/OSD with embedded switching regulator , the battery supply). Also consider any servos connected to the 5v on the FC.

Options to consider in order of recommendation of least effective to most effective are:

  • Use a good ground wiring layout design to a common point (consider this mandatory)
  • Use a high value electrolytic cap on supply lines (3300uf, 16v for 4s. 25v better but larger)
  • Use a Low ESR, high value cap on the supply lines (1000uf, 16v low ESR for 4s. 25v better but larger).
  • Use a traditional inductor / capacitor (LC) filter on the supply lines to the electronics
  • Use a linear voltage regulator circuit (7805/7812 etc)

For overvoltage protection: Consider use of a protection diode (BZX79C5V6)


  • Check camera compatibility document
You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.
Press h to open a hovercard with more details.