The default settings in the MW OSD on my configuration resulted in the artificial horizon on the roll axis being reversed.
Edit two settings in the MW OSD firmware.
In config.h, uncomment "REVERSEAHI" as below;
#define REVERSEAHI // Reverse pitch / roll direction of AHI - for DJI / Eastern bloc OSD users
In screen.ino, I used these settings;
#if defined REVERSEAHI
The purpose of this build log is to document the process of building a ZMR250 quadcopter complete with FPV and telemetry. My experience building a previous ZMR250 has been that simple problems like outdated firmware can cause major headaches and heaps of Google searching / forum reading to find the solution. The plan here is to document each step no-matter how seemingly simple it may seem
ZMR250 V2.1 Mini Quad Frame Kit w/PDB Special Edition - https://youtu.be/fLsN_18vMz8?t=91
I need to activate PPM input to the Naze32 board from the Orangerx UHF running OpenLRSng. PPM input is needed so I can use RC5 pin to control some WS2812 addressable LEDs.
The solution process:
In the Cleanflight configurator, enable RX_PPM. Connect the receiver Port 6 output to the RC input pin 1 of the Naze32 board. The problem is when I do that, and switch on the transmitter (ie the PPM stream is presented to the Naze32 input), the Naze 32 seems to lag horribly. Connecting it to the configurator takes ages for the screen to refresh.
I found disabling Telemetry in the openLRSng options for the orangerx Tx module seemed to fix the problem of the Naze32 board lagging. Now I can use the RC5 pin on the Naze32 board to control the addressable LEDs (WS2812).
The only remaining issue is that appears after arming once, then disarming, I can't re-arm with completely removing power from the Naze32.