I have a Crius MultiWii Lite FC board, expanded with a Compass & Barometer I2C module.
It works perfectly! Can use ANGLE mode, BARO altitude holding, MAG heading hold etc etc.
Zero I2C errors reported. All working well. Running standard MultiWii v2.2. Perfect!
I have added a Crius OC-16 OLED LCD Display to show telemetry data.
My config.h contains the following:
Code: Select all
#define OLED_I2C_128x64
#define LCD_MENU_PREV 'p' // These are not actually needed as I have no buttons?!
#define LCD_MENU_NEXT 'n'
#define LCD_VALUE_UP 'u'
#define LCD_VALUE_DOWN 'd'
#define LCD_MENU_SAVE_EXIT 's'
#define LCD_MENU_ABORT 'x'
#define LCD_CONF // Also probably not needed as I'm not going to use it for config?!
#define LCD_TELEMETRY // This is what I really want!!!
#define LCD_TELEMETRY_AUTO "212232425262729"
Here's the problem:
1) The MultiWii boots and initializes the LCD.
2) I get a "logo" screen showing a little quad picture and splash texts.
3) After a second the display changes to "MultiWii v2.2 Quad-X"
4) Then, nothing, no change. The "MultiWii v2.2 Quad-X" text remains on-screen forever.
I really believe that this is not an electronic issue with the OLED LCD module.
Debug still shows 0 (zero) I2C errors.
All the other I2C devices (Baro, Mago etc) all work fine.
It's like the MultiWii main loop is not switching between the different telemetry pages.
Questions:
1) Is it a problem with my config.h file?
2) Does the MultiWii only loop through its telemetry pages as defined by #define LCD_TELEMETRY_AUTO "212232425262729" when the flight control is ARMED?
Please help!
Cheers!
city_kid