Setting up OSDoge (MWOSD) with Naze32 running Cleanflight Being brand new to OSDoge, MWOSD and Cleanflight I thought I would share what I learned to make it all work together. For the most part it was straight forward but I did encounter a couple of things that might not be obvious. My hardware wiring setup I’m using an Attopilot 90a current sensor which I’m connecting directly to the Naze32 because of its higher resolution ADC as opposed to the OSDoge. This is the preferred method according to the Doge’s designer. I’m not using a GPS so connections are simple. The only connections to the OSDoge are flight battery, Vtx and CCD Camera (other than the direct connections made by stacking the boards). Connected to the Naze is a DTF UHF Rx, current sensor and 2812b LED strip signal lead (optional of course but a hell of a lot of fun). That’s it! I love what a clean solution OSDoge provides. Firmware Versions I tried various firmware versions of both Cleanflight and MWOSD but this is what worked for me. Cleanflight 1.7 (must use configurator .61) MWOSD 1.3 pre4

Setting up Cleanflight This is pretty much the same as Baseflight but there are some differences. These are the CLI commands you will need… feature RX_PPM feature CURRENT_METER set current_meter_scale = 600 (this should be set to your current sensor. I’m still playing with the value) set current_meter_offset = 0 set multiwii_current_meter_output = 0 set current_meter_type = 1 I believe that in Baseflight you must tell the controller which AUX channel to use for the power ADC but in Cleanflight it will automatically use channel 8 (pin 10). Please note that

set current_meter_type = 1 is new as of Cleanflight 1.7 (but it might have been in 1.6 as well). Don’t forget this command and set it according to your configuration. Here is the documentation on the command… https://github.com/cleanflight/cleanflight/blob/master/docs/Battery.md#current-monitoring Setting up MWOSD You will need to make some changes to the config.h file which is accessible from the Arduino editing environment. The changes are… You need to uncomment this define statement… #define CLEANFLIGHT

// Undefine this if you are using CLEANFLIGHT with 32bit hardware for compatibility with heading and current data

and set your sensor size…( I set mine to 900 because I have a 90a sensor) #define AMPERAGEMAX

900

// Size of current sensor / maximum current draw (* 10) e.g. 50A sensor = 500, 100A sensor = 1000

From the MWOSD GUI you will set up things something like this.

You will notice that current and RSSI use MWii as the display data is just being passed by the Naze32 through the serial connection to the OSDoge. I’m using DTF UHF Rx and the RSSI

information is being injected into the PPM stream, which is a feature of OpenLRSng. Your Rx may be different and you should configure accordingly. Voltage is being taken directly from the OSDoge as it is connected to the flight battery, however, you could use the measurement from the Naze as it also has a connection to the battery when the boards are stacked. Why won’t it work? After setting all this up I was not getting any current readings from either the Naze32 (you can see current and voltage information in the setup tab of the Cleanflight GUI) or the OSD. After scratching my head and checking everything I discovered that you must enable Vbat on the Naze32. Now because I’m reading voltage directly on the OSDoge, I didn’t enable this feature. In fact I believed it needed to be disabled. But once I did enable it, as an act of desperation, the current readings started working. This is a bug. Hydra (Cleanflight developer) was helping me at the time and he checked the code. He found the dependency between current meter and Vbat and he believes it should not exist. He made a quick fix and provided me with a .hex to try and of course it worked. Since Cleanflight 1.7 was just released and it still contains the bug, there will be a maintenance release soon to address it. For the time being if you are using 1.7 just enable Vbat and you’ll be good to go. That’s it! Happy FPVing. Tr3TopFlyer